How to convert the HTTP protocol to HTTPS (SSL) for NetWeaver AS Java

1. Change the port mapping of the HTTP Provider Service (ProxyMappings property) on the Java dispatcher. Use the Visual Administrator tool to perform this configuration task.

2. Open the Properties tab of the HTTP Provider Service running on the dispatcher.

Define the port mapping as a value of the ProxyMappings property. The value represents a comma-separated list of multiple port mappings.A single port mapping has the following format:

<Port to be mapped> =(Host:<hostname>,Port:<port number>,Scheme:<scheme>,Override:<true/false>)

By default the "Override: attribute" has a value of false. That is, if the client request contains information about the client's host and port, the HTTP Provider Service does not override its values with the values of the corresponding attributes of the ProxyMappings property. However, if no host and port information is present in the request, it takes the values of the Host: and Port: attributes of the property and sets them to the response. If, on the other hand, you set the Override: attribute to true, the values of the Host: and Port: attributes are always set to the response even if the request contained host and port information.

Defining a Single Mapping

If you have your engine installed on host localhost and port 50000 and want to map it to your proxy server with host name www.sap.com and port 80, enter the following as a value of the ProxyMappings property:50000=(Host:www.sap.com,Port:80,Scheme:http,Override:true)

Defining Multiple Mappings

If, in addition to the above mapping, you want to open port 50001 on host localhost on your engine and map it to port 443 on your proxy server with host name www.sap.com for HTTPS requests, enter the following as a value of the ProxyMappings property:50000=(Host:www.sap.com,Port:80,Scheme:http,Override:true),50001=(Host:www.sap.com,Port:443,Scheme:https,Override:true)
You should map only one host to a given proxy port! Multiple hosts per port mappings may not work as expected in cases of HTTP 1.0 clients.

3. Choose Update to add it to the list of properties.

4. To apply these changes, choose Save Properties.

Differences between SAP Netweaver EP and EPC

In SAP Netweaver we have had two Portal usage types (UT):

* EP: Enterprise Portal
* EPC: Enterprise Portal - Core

Q: What is actually the difference between the EP and EPC?

A: EP stands for Enterprise Portal – the well-known SAP Portal installation that includes all Portal components and functionality. EPC stands for Enterprise Portal - Core – is a leaner installation of the Portal that includes only the core Portal functionality without additional functionality such as Knowledge Management, Collaboration, etc.

Q: When should I use each usage type?

A: If you are implementing a full Enterprise Portal, you should go for EP because this gives you a full Enterprise Portal with all Portal functionality, Web Page Composer (WPC), Knowledge Management, Collaboration, and so on. If you are looking for a leaner installation that consumes less memory, disk size and other resources, you should install EPC. Keep in mind that you can move from EPC to EP at any stage.

Q: How are these usage types distinguished in the SAP NetWeaver installer?

A: For EPC installations, you should select EP Core (in addition to the other components that you want to install), as seen in screenshot below.

To install EP, you should select EP (in addition to the other components that you want to install).

Integration Non-SAP J2EE-based Web Applications into SAP Portal with SSO

Overview of Integration

To perform this integration must take into account the following steps:

1. Deployment of the portal application for the creation of the system portal object
2. Create and set the type of Application Integrator iView that will contain the applications to integrate.
3. Installing SAPSSOEXT and SAPSECU libraries
4. Deployment of the application gateway called SsoGatewayWeb
5. Changing the target application.

This integration has the following restrictions:


1. It applies only for web applications based on J2EE Servlet.
2. Depend exclusively on the sucessful load of the libraries supported by SAP (sapssoext and sapsecu) in both Windows and UNIX environments.
3. The target application must have created a profile for the user id logged to the SAP portal, this should be equal to the id with which the logged user is in the portal.
4. It must have well-defined a web resource in the target application that allows the "login" to be used by iView of type "Application Integrator".
5. This solution is only applied to a SAP NetWeaver Portal 7.0.

These steps are broadly outlined below each of these steps.

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.