cancel
Showing results for 
Search instead for 
Did you mean: 

Alias for a portal component

Former Member
0 Kudos

Hi All

We can call a portal component directly with the URL [http://<server>:<port>/irj/servlet/prt/portal/prtroot/AppName.ComponentName]. How do we call this component using an URL like this - [http://<server>:<port>/irj/xyz] ?

I did try to modify the web.xml of the /irj (by adding an alias for the java class), however couldn't achieve it. (Also tried with quicklinks too, however that gives a desktop which is not the requirment. Cannot go for a dispatcher / reverse proxy as the same is not being used in the current scope.)

Thanks

Deepak

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member187977
Participant
0 Kudos

hi Deepak,

you said yu tried with quicklinks too but it assings a desktop which is not the requirement. What does this mean ? As suggested by Ramganeshan and as have been tried by me, it is possible to access portal components using quicklinks.

thank you !

seventyros

Learn SAP EP

former_member189631
Active Contributor
0 Kudos

Hi Deepak,

Another simple way would be create an iView for your portal componenet, assign to a page, assign the page to a role. Add the role to user and assign a name to the quicklink property of the page.

You can now access your application in the following way:

http://<portalserver>:<port>/irj/portal/<quicklinkname>

Thanks.

Ram

hofmann
Active Contributor
0 Kudos

Hi,

it's not easily possible to map a URL like /irj/xyz to a custom application. That's not how the portal is working. For instance, in your web.xml, you mapped xyz to the gateway servlet. The gateway servlet analyzes the URL and invokes the portal dispatcher, depending on the paramter. And alias parameters configured in web.xml are used to assign a desktop.

You can use the alias configuration to configure a "headless" portal that will load the necessary javascript files but not all the other overhead normally used to facilitate the integration of portal iViews into other portal (like IBM).

What you can try to do is to create the URL /xyz (EAR, create a HTML file in the root /, web server alias in VA, etc) and map this URL to your application, directly or by iFrame.

br,

Tobias

Former Member
0 Kudos

Hi Tobias

Thank you so much for your confirmation regarding the complexities involved in customization of the URL.

Since, there were no much updates on this thread, I had started developing a web application that will give the URL as required and the app is working good.

Thanks

Deepak

former_member187977
Participant
0 Kudos

hi,

In the standard URL of a portal component, what does appName stand for? Where can we find the appName of a portal component ?

thank you

seventyros

Learn SAP EP

Former Member
0 Kudos

Hi Deepak,

Creating an alias requires a restart of the Portal Server. Can you please restart and then try again.

Also, can you please post your web.xml here.

Thanks,

Nikhil

Former Member
0 Kudos

Hi Nikhil

I did server restart too. Yet no luck. Here is the web.xml of /irj:



<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
<!--

This is the servlet definition for the iView Runtime Java.

-->
<web-app>
	<display-name>The Java iView Runtime</display-name>
	<listener>
		<listener-class>
            com.sapportals.portal.prt.session.HttpSessionHandler
        </listener-class>
	</listener>
	<servlet>
	      <servlet-name>
		gateway
	      </servlet-name>
	      <servlet-class>
		com.sap.portal.navigation.Gateway
	      </servlet-class>
	      <load-on-startup>
		0
	      </load-on-startup>

	      <init-param>
		<param-name>
			portal_entry_point
		</param-name>
		<param-value>
		               /servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default
		</param-value>
	      </init-param>

	   <init-param>
		<param-name>
			xyz_entry_point
		</param-name>
		<param-value>
			/servlet/prt/portal/prtroot/com.abc.sales.xyzApp.XYZComp
		</param-value>
	      </init-param>

	      <init-param>
		<param-name>
		          wsrp_producer_service
		</param-name>
		<param-value>
		           ProducerImpl
		</param-value>
	      </init-param>

	      <init-param>
		<param-name>
			portal_anonymous_entry_point
		</param-name>
		<param-value>
			/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.anonymous
		</param-value>
	      </init-param>
	      <init-param>
		<param-name>
			 portal
		</param-name>
		<param-value>
		 anonymous=0,proxy=0,low_bandwidth=0,include_in_url=1,include_application_name_in_url=1
		</param-value>
	      </init-param>

	<init-param>
		<param-name>
			 xyz
		</param-name>
		<param-value>
		 anonymous=0,proxy=0,low_bandwidth=0,include_in_url=1,include_application_name_in_url=1
		</param-value>
                   </init-param>

	      <init-param>
		<param-name>
			 portal/collaboration
		</param-name>
		<param-value>
		 anonymous=0,proxy=0,low_bandwidth=0,include_in_url=1,include_application_name_in_url=1
		</param-value>
	      </init-param>

	    <init-param>
		<param-name>
                                   		 portal/ajax
		</param-name>
		<param-value>
		 anonymous=0,proxy=0,low_bandwidth=1,include_in_url=1,include_application_name_in_url=1
		</param-value>
	</init-param>

	    <init-param>
		<param-name>
			 portal/aboutme
		</param-name>
		<param-value>
		 anonymous=0,proxy=0,low_bandwidth=0,include_in_url=1,include_application_name_in_url=1
		</param-value>
	      </init-param>

	      <init-param>
		<param-name>
			 portal/light
		</param-name>
		<param-value>
		 anonymous=0,proxy=0,low_bandwidth=1,include_in_url=1,include_application_name_in_url=1
		</param-value>
	      </init-param>

	      <init-param>
		<param-name>
			 portal/anonymous
		</param-name>
		<param-value>
		 anonymous=1,proxy=0,low_bandwidth=0,include_in_url=1,include_application_name_in_url=1
		</param-value>
	      </init-param>
	</servlet>

	<servlet>
		<servlet-name>prt</servlet-name>
		<servlet-class>com.sapportals.portal.prt.dispatcher.Dispatcher</servlet-class>
		<load-on-startup>1</load-on-startup>
	        <init-param>
		<param-name>
			portal_context_root
		</param-name>
		<param-value>
			/irj
		</param-value>
	      </init-param>

	</servlet>

	<servlet-mapping>
		<servlet-name>gateway</servlet-name>
		<url-pattern>/portal/*</url-pattern>
	</servlet-mapping>

	<servlet-mapping>
		<servlet-name>gateway</servlet-name>
		<url-pattern>/xyz/*</url-pattern>
	</servlet-mapping>


                   <servlet-mapping>
		<servlet-name>gateway</servlet-name>
		<url-pattern>/wsrp/producer/resource/*</url-pattern>
	</servlet-mapping>
	<servlet-mapping>
		<servlet-name>gateway</servlet-name>
		<url-pattern>/wsrp/consumer/resource/*</url-pattern>
	</servlet-mapping>
	<servlet-mapping>
		<servlet-name>prt</servlet-name>
		<url-pattern>/irj/*</url-pattern>
	</servlet-mapping>
	<servlet-mapping>
		<servlet-name>prt</servlet-name>
		<url-pattern>/go/*</url-pattern>
	</servlet-mapping>


	<welcome-file-list>
		<welcome-file>index.html</welcome-file>
		<welcome-file>index.jsp</welcome-file>
	</welcome-file-list>
</web-app>


Thanks

Deepak

former_member201257
Active Contributor
0 Kudos

Please note that the changes should be made in all the server nodes.

/usr/sap/<SID>/<INSTANCE>/j2ee/cluster/serverN/apps/sap.com/irj/servlet_jsp/irj/root/web-inf

Former Member
0 Kudos

Hi Shanti

Changes were applied to all server nodes too. Problem still persists.

Thanks

Deepak