This section contains the following procedures:
This section describes how to configure a Portal Server and a Gateway on a single node in the Configure Now and Configure Later modes.
Using the Configure Now mode, you can configure a Gateway while installing Portal Server, where the Gateway is configured with other components. You can also configure the Gateway using the Configure Later mode, where you need to manually configure Gateway using the psconfig command after installing Portal Server.
Select the Gateway option displayed with Sun Java System Portal Server Secure Remote Access 7.1 when you install Sun Java System Portal Server 7.1.
Enter Directory Server, Access Manager, and web container information in the Java ES installer screens.
Start Directory Server and web container instance after a successful installation of Portal Server.
Start the gateway.
PortalServer_base/SUNWportal/bin/psadmin switch-sra-status -u admin-user-name -f password-file on
PortalServer_base/SUNWportal/bin/psadmin provision-sra -u admin-user-name -f password-file --gateway-profile gateway_profile --enable
PortalServer_base/SUNWportal/bin/psadmin start-sra-instance -u admin-user-name -f password-file -N default -t gateway
Select Sun Java System Portal Server 7.1, Directory Server, and web container in the Java ES installer.
Select the Gateway option displayed with Sun Java System Portal Server Secure Remote Access 7.1.
Install the components using the Java ES installer in the Configure Later mode.
Ensure that Directory Server, web container instance, and web container administrator server are running.
Modify the example7.xml file.
The example7.xml file is located in the PortalServer_base/SUNWportal/samples/psconfig directory.
Configure common agent container.
PortalServer_base/SUNWportal/bin/psconfig --config example7.xml
Start the Gateway.
PortalServer_base/SUNWportal/bin/psadmin switch-sra-status -u admin-user-name -f password-file on
PortalServer_base/SUNWportal/bin/psadmin provision-sra -u admin-user-name -f password-file --gateway-profile gateway_profile --enable
PortalServer_base/SUNWportal/bin/psadmin start-sra-instance -u admin-user-name -f password-file -N default -t gateway
This section describes how to configure Portal Server and Gateway on separate nodes in the Configure Now and Configure Later modes.
Using the Configure Now mode, you can configure a Gateway while installing the Portal Server, where the Gateway is configured with other components. You can also configure the Gateway using the Configure Later mode, where you need to manually configure Gateway using the psconfig command after installing Portal Server.
Ensure that the following ports are opened whenever you configure a Gateway or perform any administrator console or command line operations that involve Gateway.
11162 : JMX Port (TCP)
11161 : SNMP Adapter Port (UDP)
11163 : Commandstream Adapter Port (TCP)
11164: RMI Connector Port (TCP)
This procedure requires two nodes: Node 1 and Node 2.
Install Portal Server and Directory Server in the Configure Now mode on Node 1.
Select Enable SRA for Portal while installing the Portal Server.
(Optional) Set SRA status to Enabled on Node 1, if the Enable SRA for Portal is not selected while installing.
PortalServer_base/SUNWportal/bin/psadmin switch-sra-status -u admin_user -f password_file on
Start the Java ES installer and install Access Manager SDK and Gateway on Node 2 in the Configure Now mode.
Use the same password encryption key on both the nodes.
Enable Gateway profile on Node 1.
PortalServer_base/SUNWportal/bin/psadmin provision-sra -u admin_user -f password_file --gateway-profile gateway_profile --enable
Start the SRA instance on Node 2.
PortalServer_base/SUNWportal/bin/psadmin switch-sra-status -u admin-user-name -f password-file on
PortalServer_base/SUNWportal/bin/psadmin provision-sra -u admin-user-name -f password-file --gateway-profile gateway_profile --enable
PortalServer_base/SUNWportal/bin/psadmin start-sra-instance -u admin-user-name -f password-file -N default -t gateway
Install Portal Server and Directory Server on Node 1 in the Configure Now mode.
Install AMSDK on Node 2 in the Configure Now mode using the Java ES installer.
Use the same password encryption key on both the nodes.
Install Gateway on Node 2 in the Configure Later mode using the Java ES installer.
Enable Gateway profile on Node 1.
PortalServer_base/SUNWportal/bin provision-sra -u admin_user -f password_file --gateway-profile gateway_profile --enable
Modify the example10.xml file.
The example10.xml file is located in the PortalServer_base/SUNWportal/samples/psconfig directory.
Configure common agent container.
PortalServer_base/SUNWportal/bin/psconfig --config example10.xml
Start the Gateway.
PortalServer_base/SUNWportal/bin/psadmin switch-sra-status -u admin-user-name -f password-file on
PortalServer_base/SUNWportal/bin/psadmin provision-sra -u admin-user-name -f password-file --gateway-profile gateway_profile --enable
PortalServer_base/SUNWportal/bin/psadmin start-sra-instance -u admin-user-name -f password-file -N default -t gateway
Install Directory Server and Application Server.
Start Directory Server and Application Server.
Create a node agent.
asadmin create-node-agent --user admin --password password --savemasterpassword=true node1
Start the node agent.
./asadmin start-node-agent --user admin --password password node1
Create non default server instance.
./asadmin create-instance --user admin --password password --nodeagent node1 server1
Start the instance.
./asadmin start-instance --user admin --password password server1
Install Access Manager in the Configure Later mode.
Edit the amsamplesilent file.
Restart Directory Server, Application Server, and Access Manager.
Check if Access manager is up and running.
Invoke installer and install Portal Server in the Configure Later mode.
Edit the example14.xml file and configure common agent container.
./psconfig --config example14.xml
Installing the Gateway with Portal Server in SSL mode allows the user, in the same Intranet where Portal Server is installed, to access Portals through a secure protocol.
Import the root Certificate Authority (CA) to the certificate database.
cd /usr/jdk/entsys-j2se/jre/lib/security /usr/jdk/entsys-j2se/jre/bin/keytool -keystore cacerts -keyalg RSA -import -trustcacerts -alias alias-name -storepass store-password -file file-name-path |
Start the Java ES installer and install the Gateway and Access Manager SDK.
Create a certificate signing request.
Get this certificate signed by the Certificate Authority.
The Certificate Authority will be the Portal Server Administrator.
Create a file on the Gateway node, and paste the certificate response.
Add the signed certificate to the certificate database of Gateway.
Add the Root Certificate Authority to the certificate database.
Restart the Gateway.
PortalServer_base/SUNWportal/bin/psadmin switch-sra-status -u admin-user-name -f password-file on
PortalServer_base/SUNWportal/bin/psadmin provision-sra -u admin-user-name -f password-file --gateway-profile gateway_profile --enable
PortalServer_base/SUNWportal/bin/psadmin start-sra-instance -u admin-user-name -f password-file -N default -t gateway
You can also create an instance of Gateway. This allows the user to contact any one of the Gateway instances and access Portals.
Log in to Portal Server administrator console.
Click the Secure Remote Access tab.
Click New Profile.
Type the new profile name and select the Copy Profile Data From option. Click OK.
The following message is displayed: “New profile is successfully created. Please change the relevant ports in the new profile so that they do not clash with those in the existing profiles.”
Click OK.
The Profile screen is displayed.
Click the new profile created and change the port of the instance so that it does not clash with any ports that are in use.
You need to change both the http and https port numbers.
Click OK.