Installing JSR168 Sample Portlets and WSRP Samples on Third-Party Web Containers
After Portal Server and Access Manager SDK have been installed using Java Enterprise Server installer, use one of the following procedures to install JSR168 sample portlets or WSRP samples. If you use BEA WebLogic Server™ or IBM WebSphere® Application Server, install both JSR168 sample portlets and WSRP samples. If you use Sun Java System Web Server or Sun Java System Application Server, install the WSRP samples.
Note –
Mobile Access does not support IBM WebSphere or BEA WebLogic.
To Install JSR168 Sample Portlets and WSRP Samples On BEA WebLogic or
IBM WebSphere
Before You Begin
The following procedure applies only to Portal Server installations on the Solaris platform.
Steps
-
Restart the BEA WebLogic 8.1 or IBM WebSphere Application Server 5.1 instance.
-
Execute the following commands to install JSR168 Portlet samples.
PortalServer-base/lib/postinstall_PortletSamples
Provide the Access Manager admin password and application server admin password when prompted.
The portletsamples.war file is deployed.
-
Make sure that the PATH setting includes /usr/bin. This is needed for awk part of script to run correctly.
-
Execute the following commands to configure WSRP samples.
To Install WSRP Samples On Web Server or Application Server
Before You Begin
The following manual steps are needed after the Portal Server and Access Manager SDK have been installed on Sun Java System Web Server 6.1 and Sun Java Server Application Server 7:
Steps
-
Restart the Web Server or Application Server instance
-
Make sure that the PATH setting includes /usr/bin. This is needed for awk part of script to run correctly.
-
Execute the following commands to configure the WSRP samples.
-
PortalServer-base/samples/wsrpproducer/producersampleconfig
Provide the Access Manager admin password when prompted.
-
PortalServer-base/samples/wsrpconsumer/consumersampleconfig
Provide the Access Manager admin password when prompted.
-
Secure Remote Access
When a user session time out or user session logout action happens, the Sun Java System Identity Server sends a session notification to the gateway. Even when the Sun Java System Identity Server is running in HTTP mode, it will act as an SSL client using HttpsURLConnection to send the notification. Since it is connecting to an SSL server (the gateway), it should have the gateway CA certificate as part of the Trusted CA list or it should have an option to allow self signed certificate.
Note –
The method for adding the CA to the trusted CA list depends on the protocol handler defined.
To create HttpsURLConnection, the Java Virtual Machine (JVM™) property -Djava.protocol.handler.pkgs needs to be set.
If Portal Server is running on the Sun Java System Web Server, Sun Java System Application Server, or BEA WebLogic Server, this property is correctly set to com.iplanet.services.com by default. The Sun Java System Identity Server package has the implementation of HttpsURLConnection and it provides an option to accept self-signed certificates from any SSL server by adding the flag com.iplanet.am.jssproxy.trustAllServerCerts=true in the AMConfig.properties file.
The -Djava.protocol.handler.pkgs is not set by default for the IBM WebSphere Application Server. The HttpsURLConnection implementation for supported application servers must use their own default handler (this could be JSSE or custom SSL implementation).
Configuring Multiple Gateways on Multiple Portals
When installing a second gateway on a second portal, you must manually update the Forward Cookie URLs value to point to the second Portal.
Steps
-
Log in to the Access Manager Administration Console.
-
Select the Service Configuration tab.
-
Click Gateway.
-
Add the second Portal to the Forward Cookie URLs list.
Starting and Stopping the Gateway
Steps
-
Start the gateway using the following command:
gateway-base/SUNWps/bin/gateway -n new-profile-name start
default is the default name of the gateway profile that is created during installation. You can create your own profiles later, and restart the gateway with the new profile. See “Creating a Gateway Profile” in Chapter 2 of the Sun Java System Portal Server, Secure Remote Access 6 2005Q1 Administration Guide.
If you have multiple gateway instances, use:
gateway-base/SUNWps/bin/gateway start
Note –This step is not required if you chose y for the Start Gateway after installation option during the gateway installation.
Note –Ensure that only the configuration files for the instances that you want to start are in the /etc/opt/SUNWps directory.
If you want to stop all the gateway instances that are running on that particular node, use the following command:
gateway-base/SUNWps/bin/gateway stop
The Netlet and the gateway need Rhino JavaScript™ parser (bundled as SUNWrhino) for PAC file support. This must be installed in the Gateway and Portal Server node. To install, use the following steps:
-
Add this package by running pkgadd -d . SUNWrhino from the current directory.
-
Copy package-base-dir/js.jar to
${JAVA_HOME}/jre/lib/ext directory.
Netlet and Rewriter Proxy
Before starting the Netlet Proxy and the Rewriter Proxy, ensure that the gateway profile is updated with the Netlet Proxy and the Rewriter Proxy options.
-
If you did not choose the option to start the Netlet Proxy during installation, you can start the Netlet Proxy manually. In the directory, portal-proxy-base/SUNWps/bin, type:
./netletd -n default start
-
If you did not choose the option to start the Rewriter Proxy manually during installation, you can start it manually. In the directory portal-proxy-base/SUNWps/bin, type:
./rwproxyd -n default start
Note –
Ensure that you enable the Access List service for all users, to allow access through the gateway.
The Sun Java System Portal Server software NetFile needs jCIFS libraries (bundled as SUNWjcifs) for Windows access. This needs to be installed in Portal Server node only. To install, use the following steps.
To Install the jCIFS Libraries
Steps
- © 2010, Oracle Corporation and/or its affiliates