How to .. Integration Non-SAP J2EE-based Web Applications into SAP Portal with SSO Part 1
+*Detailed Description. *
*1. *+*Deployment of the application for establishment of portal partner. *+ We will need to deploy the application of type “Portal Application” on the portal. The name of such applications is: com.cts.portal.appintegrator.webapp.par (link) To install this applied to the portal will use the iView prescribed in: “System Administration”> “Support”> Link “Portal Runtime”> “Administration Console”. To perform the action “Upload” ont “com.cts.portal.appintegrator.webapp.par” file as shown in Figure 1. Figura 1. Admnistration console – “Portal Anywhere Admin Tools” The purpose of this portal application is to define an object of the type “system” that will use with the Application Integrator component. Now create the system object type in the PCD, based on the deployed file. For this we must go to the iView “System Landscape Editor”: “System Administration”> “System Configuration”> “System Landscape. Next, we will create a template system that use to create system objects to be used individually by each iView of this type, as discussed below. +*2.Template Creation System. *+ we will need to create a folder within “Portal Content” / “My Personal Content” with the same name of the application to integrate. Within it we’ll create the folders: iView, Role and System. a. Inside the folder “system” will create an object “system” by making use the option “System from PAR”, see the Figure 2. Figure 2. Creation of the System Template b. Choose the option “com.cts.portal.appintegrator.webapp” associated with the portal application already deployed. c. In Step 2, choose the unique option shown: WebApplicationIntegrator d. In the step 3, complete the following information: System Name: Web Application System ID: WebApplicationIntegrator System ID Prefix: com.cts.portal.appintegrator.webapp. Then we click on the button “Finish” and choose to open the object for editing, where you choose “Yes” in the attribute “Is a Template”. See Figure 3. Figure 3. Edit Object “Template System. Finally, we must save the changes. And we have created a template system that will be used for any type SSO integracción using the Application Integrator. Next, we are going to detail the steps to integrate any web J2EE applications in the SAP Portal using SSO. In this case we show the integration of the application “My Struts Demo Web” which is deployed in an application server instance (SAP Netweaver Application Server 7.0). Before proceeding we should have in mind: 0.1. Must be configured Single Sign-On between both servers. 0.2. The target server must accept SAP Logon Ticket. 0.3. The servers to integrate must be in the same domain, in this special case: mydomain.com.pe 0.4. Every communication must be using the POST method and possibly encrypted communications using SSL, HTTPS could be configured on both servers *+3. Creation of System “MyCustomizeStrutsSSO” +* Now we will create an object system from the previously created template. Shown in Figure 4. Figure 4. Creation of system MyCustomizeStrutsSSO 1. First, we will choose the option “Web Application”, as in Figure 5. Figure 5. Template Selection 2. In Step 2, fill the following information: System Name: Talking to Management System ID: MyCustomizeStrutsSSO. System ID Prefix: pe.com.mydomain.ssointegration Then we click on the button “Finish” and open the object for editing. 3. Within the “Property Editor”, choose from the attribute “Property Category” (the drop down component) the option: “Show All by Category”. 4. In the group “System Definition” adds the following values. Name of Server: myserver1.mydomain.com.pe Port Number: 50100 Protocol of the Target system: http URI of the web application: /strutsdemoweb/autentificar.do Here the values that could vary, for this demonstration applications would be the server name, port number and perhaps the protocol of the target system. 5. In the group of attributes “UserManagment, put the following values: Logon Method: SAPLOGONTICKET User Mapping Type: User See Figure 6.