test

Sun Java System Portal Server 6 2005Q4 Release Notes

About Portal Server 6 2005Q4

The Sun Java System Portal Server 6 product gives end users a portal Desktop, which provides access to resources and applications. The Portal Server software also provides a search engine infrastructure that enables intranet content to be organized and accessed from the portal Desktop. Additionally, in this release, the Communication Channels are now installed with the Portal Server software. The communication channels consist of mail, calendar, address book, and instant messaging channels.

Portal Server also offers Secure Remote Access support, which enables remote users to securely access their organization’s network and its services over the Internet. Additionally, it gives your organization a secure Internet portal, providing access to content, applications, and data to any targeted audience--employees, business partners, or the general public.

This release of Sun Java System Portal Server is a maintenance release and contains no new features.

This section includes:

More Information About This Release

In Sun Java Studio Creator 2, support has been added for JSR-168 JSF Portlets. Portlets created in the Creator 2 tool can be deployed to Sun Java Portal Server 6.3.1. To learn more about Sun Java Studio Creator 2 and it's Portlet supports, see:

Sun Java Studio Creator

http://developers.sun.com/prodtech/javatools/jscreator

Java Studio Creator 2

http://developers.sun.com/prodtech/javatools/jscreator

Creating Portlets in Sun Java Studio Creator 2

http://developers.sun.com/prodtech/javatools/jscreator/reference/fi/portlets.html

Deploying a Portlet Application

http://developers.sun.com/prodtech/javatools/jscreator/reference/techart/2/portlet_deploy.html

Hardware and Software Requirements for Solaris

The following hardware and software are required for this release of Portal Server.

Table 2 SolarisTM Hardware and Software Requirements

Component  

Platform Requirement  

Supported Platforms 

Sun UltraTM 60 or Sun Blade comparable or better workstation

Operating System 

SolarisTM 8, SolarisTM 9U6, or SolarisTM 10 for OS requirement

RAM 

512 Mbytes of RAM for evaluation install 

1.2 Gbytes of RAM for regular deployment 

Disk space 

1 Gbyte of disk space for Portal Server and associated applications 

Swap size 

100 Mbytes. 

Hardware and Software Requirements for Linux

Table 3 Linux Hardware and Software Requirements

Component  

Platform Requirement  

Operating System 

Linux RedHat EL AS 2.1 u2 

Linux RedHat 3.0 

RAM 

512 Mbytes of RAM for evaluation install 

1.2 Gbytes of RAM for regular deployment 

Disk space 

1 Gbyte of disk space for Portal Server and associated applications 

For software requirements, see the Sun Java Enterprise System Release Notes at http://docs.sun.com.

Default Paths and File Names

The following table describes the default paths and file names used in this book.

Table 4 Default Paths and File Names

Term  

Description  

PortalServer-base

Represents the base installation directory for Portal Server. The Portal Server 2005Q4 default base installation and product directory depends on your specific platform: 

Solaris™ systems /opt

Linux systems: /opt/sun

For example, if the install root is /opt (the default) the Portal Server is installed in /opt/sun/portal for Linux platforms and /opt/SUNWps for Solaris platforms.

AccessManager-base

Represents the base installation directory for Access Manager. The Access Manager 2005Q4 default base installation and product directory depends on your specific platform: 

SolarisTM systems: /opt/SUNWam

Linux systems: /opt/sun/identity

DirectoryServer-base

Represents the base installation directory for Sun Java System Directory Server. Refer to the product documentation for the specific path name. 

ApplicationServer-base

Represents the base installation directory for Sun Java System Application Server. Refer to the product documentation for the specific path name. 

WebServer-base

Represents the base installation directory for Sun Java System Web Server, or BEA WEblogic 8.1 SP2, or IBM WebSphere. Refer to the product documentation for the specific path name. 

Post Installation Configuration

This section is organized as follows:

The psconfig Script

If you have installed Portal Server with the Sun Java Enterprise System installer with the “Configure Later” option, use psconfig to configure the Portal Server component product. The following checklists in this section describe the parameters used to configure the Portal Server component product.

ProcedureTo Run the psconfig Script

Steps

  1. As root in a terminal window, go to the directory that contains the psconfig script:

    cd PortalServer-baseSUNWps/lib

  2. Configuration can be performed in either the interactive mode or using a silent file.

    Note –

    Sample pssamplesilent file is available at the location PortalServer-base/SUNWps/lib. Modify this file for your setup details before using it.

    If you have performed a minimal installation, you will need to use the psconfig script to configure your Portal Server installation. The following checklists describe the values that you will need for a post-install configuration. Depending on the type of installation you perform, the values that you use might vary.

Portal Server And Secure Remote Access Configuration Checklist

The following tables are three column tables that list all the values that you might need for a post-install configuration. Depending on the type of installation you perform, the values that you use might vary. The first column lists the parameter; the second column lists the default value; and the third column lists the description. The Checklists are organized in the following way:

Note –

The Portal Server default base installation and product directory depends on your specific platform:

Solaris™ systems /opt

Linux systems: /opt/sun

For example, if the install root is /opt (the default) the Portal Server is installed in /opt/sun/portal for Linux platforms and /opt/SUNWps for Solaris platforms.

Note –

If a parameter is not applicable to a container, it is not included in the table.

Table 5 Component Selection

Parameter 

Default Value 

Description 

COMPONENTS

Sun Java System Portal Server components to be configured 

1,2,3,4,5 

Set “1” to configure PortalServer. 

Set “2” to configure Secure Remote Access Core. 

Set “3” to configure Gateway. 

Set “4” to configure NetletProxy. 

Set “5” to configure RewriterProxy. 

To Configure multiple components, use a comma (,) to separate entries. 

Table 6 Base Directory

Parameter 

Default Value 

Description 

BASEDIR

BASEDIR

The directory where Sun Java System Portal Server configurator components are installed 

 

This is the base directory in which the Portal Server software is installed using Java Enterprise System Installer. 

The base directory depends on the platform you are using. 

For example, if the install root is /opt (the default) the Portal Server is installed in: 

/opt/sun/portal for Linux platforms 

/opt/SUNWps for Solaris platforms. 

PS_CONFIGURATION_MODE

The Configuration mode in which you want the Sun Java System configurator needs to be executed 

configure 

Possible values are: 

configure–Configure the Portal Server Components. 

scrubds–Remove the Portal Server Components entries from the Directory Server. 

unconfigurewithoutscrubds–Unconfigure the Portal Server Components without removing the entries from the Directory Server. 

unconfigurewithscrubds–Unconfigure the Portal Server and also remove the entries from the Directory Server. 

Table 7 Deployment Information

Parameter 

Default Value 

Description 

PS_DEPLOY_TYPE

The web container on which Portal Server is being deployed. The Portal Server can be deployed on: 

  • Sun Java System Web Server Table 8

  • Sun Java System Application Server 7.0 Table 9

  • Sun Java System Application Server 8.1 Table 10

  • BEA WebLogic Server Table 11

  • IBM WebSphere Application Server Table 12

SUNONE8

Possible values are: 

IWS = Sun Java System Web Server 

SUNONE = Sun Java System Application Server 7.0 

SUNONE8 = Sun Java System Application Server 8.1 

WEBLOGIC = BEA WebLogic Server 8.1 SP2 

WEBSPHERE = IBM WebSphere Application Server. 

Table 8 Sun Java System Web Server

Parameter 

Default Value 

Description 

PS_DEPLOY_DIR

/opt/SUNWwbsvr

Directory in which the Sun Java System Web Server is installed. 

PS_DEPLOY_INSTANCE

myportalbox.mydomain.com 

The web server instance you want the Portal Server to use. Note: The instance name should not contain spaces. 

PS_DEPLOY_DOCROOT

/opt/SUNWwbsvr/docs

The Web Server Directory where static pages are kept. 

PS_DEPLOY_ADMIN

admin

The administrator user ID. 

PS_DEPLOY_ADMIN_PROTOCOL

http

The administration server Protocol. 

PS_DEPLOY_ADMIN_HOST

myportalbox.mydomain.com 

The administration server hostname. 

PS_DEPLOY_ADMIN_PORT

8888

The port number of the administration server. 

PS_DEPLOY_JDK_DIR

/usr/jdk/entsys-j2se

The JDK Dir that is being used by the web container. 

Table 9 Sun Java System Application Server 7.0

Parameter 

Default Value 

Description 

PS_DEPLOY_DIR

/opt/SUNWappserver7

Directory in which the Sun Java System Application Server 7.0 is installed 

PS_DEPLOY_DOMAIN

/var/opt/SUNWappserver7/domains/domain1

The Sun Java System Application Server domain contains a set of instances. 

The domain specified will contain the instance used by the Portal Server. This domain must already be configured. 

PS_DEPLOY_INSTANCE

server1

The name of the Sun Java System Application Server instance to which the Portal Server will be deployed. 

This instance must already be configured. The instance name should not contain spaces. 

PS_DEPLOY_DOCROOT

/var/opt/SUNWappserver7/domains/domain1/server1/docroot

The Application Server Directory where static pages are kept. 

PS_DEPLOY_ADMIN

admin

The administrator user ID. 

PS_DEPLOY_ADMIN_PROTOCOL

http

The administration server Protocol. 

PS_DEPLOY_ADMIN_HOST

myportalbox.mydomain.com 

The administration server hostname. 

PS_DEPLOY_ADMIN_PORT

4848

The port number of the administration server. 

PS_DEPLOY_JDK_DIR

/usr/jdk/entsys-j2se

The JDK Dir that is being used by the we container. 

Table 10 Sun Java System Application Server 8.1

Parameter 

Default Value 

Description 

PS_DEPLOY_DIR

/opt/SUNWappserver/appserver

Directory in which the Sun Java System Application Server 8.1 is installed 

PS_DEPLOY_DOMAIN

domain1

The Sun Java System Application Server domain contains a set of instances. The domain specified will contain the instance used by the Portal Server. 

This domain must already be configured. 

PS_DEPLOY_INSTANCE_DIR

/var/opt/SUNWappserver/domains/domain1

The full path of the domain specified that will be configured for the Portal Server. 

PS_DEPLOY_INSTANCE

server

The name of the Sun Java System Application Server instance to which the Portal Server will be deployed. 

This instance must already be configured. The instance name should not contain spaces. 

PS_DEPLOY_DOCROOT

/var/opt/SUNWappserver/domains/domain1/docroot

The Application Server Directory where static pages are kept. 

PS_DEPLOY_ADMIN

admin

The administrator user ID. 

PS_DEPLOY_ADMIN_PROTOCOL

https

The administration server Protocol. 

PS_DEPLOY_ADMIN_HOST

myportalbox.mydomain.com 

The administration server hostname. 

PS_DEPLOY_ADMIN_PORT

4849

The port number of the administration server. 

PS_DEPLOY_JDK_DIR

/usr/jdk/entsys-j2se

The JDK Directory that is being used by the web container. 

Table 11 BEA WebLogic Server

Parameter 

Default Value 

Description 

PS_DEPLOY_DIR

/usr/local/bea

The directory in which BEA is installed. 

PS_DEPLOY_DOMAIN

mydomain 

The BEA WebLogic Server domain contains a set of instances. The domain specified will contain the instance used by the Portal Server. This domain must already be configured. 

PS_DEPLOY_INSTANCE

myserver 

The name of the BEA WebLogic Server instance to which the Portal Server will be deployed. 

This instance must already be configured. The name must not contain a space. 

If you are installing Portal Server on an administration server instance this will be the name of the administration server instance. Otherwise it will be the name of the managed server instance. 

PS_DEPLOY_DOCROOT

/usr/local/bea/user_projects/domains/mydomain/applications

The document root value of DefaultWebApp needs to be deployed to the BEA WebLogic Server instance on which you are running the Portal Server software. 

DefaultWebApp is the default web application, from which is served static content in a BEA WebLogic Server. By default it is only deployed to the domain (mydomain) and the server instance defined or created during the BEA WebLogic Server install. This means that if you create your own BEA WebLogic Server or domain, you need to deploy the DefaultWebApp to it, either by copying the directory to the new server’s deployment directory, or by using the BEA WebLogic Server administration console. 

See the BEA WebLogic Server documentation for more detail on how to configure a default web application. 

PS_DEPLOY_ADMIN

weblogic

The administrator user ID. 

PS_DEPLOY_ADMIN_PROTOCOL

http

The administration server Protocol. 

PS_DEPLOY_ADMIN_HOST

myportalbox.mydomain.com 

The administration server host name. 

PS_DEPLOY_ADMIN_PORT

7001

The port number of the administration server. 

PS_DEPLOY_JDK_DIR

/usr/local/bea/jdk141_03

The JDK directory that is being used by the BEA WebLogic server. 

PS_DEPLOY_PRODUCT_DIR

/usr/local/bea/weblogic81

The directory in which the BEA WebLogic Server software is installed. 

PS_DEPLOY_PROJECT_DIR

user_projects

This is the user project’s directory. Use the value you entered during BEA WebLogic installation. 

PS_DEPLOY_DOMAINS_DIR

domains

The name of the directory containing the BEA WebLogic Server domain. 

PS_WEBLOGIC_CONFIG_DIR

/usr/local/bea/user_projects/domains/mydomain

The full path of the BEA WebLogic Server domain. 

Table 12 IBM WebSphere Application Server

Parameter 

Default Value 

Description 

PS_DEPLOY_DIR

/opt/WebSphere/Express51/AppServer

The directory in which the IBM WebSphere Application Server software is installed. 

PS_DEPLOY_INSTANCE

server1

The name of the instance to which the Portal Server will be deployed. This instance must already be configured. 

Portal Server can not be installed into an application server instance or domain whose name contains a dash or a space, for example, Default-Server or Default Server. 

PS_DEPLOY_DOCROOT

/opt/IBMHTTPD/htdocs/en_US

The directory where static pages are kept. This directory is created during the Sun Java System Identity Server installation. 

PS_DEPLOY_ADMIN

admin

The administrator user ID. 

PS_DEPLOY_ADMIN_PROTOCOL

http

The administration server Protocol. 

PS_DEPLOY_ADMIN_HOST

myportalbox.mydomain.com 

The administration server host name. 

PS_DEPLOY_ADMIN_PORT

7080

The port number of the administration server. 

PS_DEPLOY_JDK_DIR

/usr/jdk/entsys-j2se

The JDK directory that is being used by the we container. 

PS_DEPLOY_NODE

myportalbox 

 

PS_DEPLOY_CELL

myportalbox 

 

PS_DEPLOY_VIRTUAL_HOST

default_host 

Use the value you entered during IBM WebSphere installation. 

Table 13 Portal Server Information

Parameter 

Default Value 

Description 

PS_DEPLOY_URI

/portal

The URI is the space on the web server or application server that the Portal Server uses. 

The value for the deployment URI must have a leading slash and must contain only one slash. However, the deployment URI can not be a "/" by itself. 

PS_LOAD_BALANCER_URL

Load balancer controlling Portal Server Instances 

http://myportalbox.mydomain.com:80/portal

If you are not using any Load Balancer URL then use the Portal Server URL. http://fully-qualified-domain:port/portal-deploy_uri

For example http://myportalbox.mydomain.com:80/portal

PS_PROTOCOL

http

The Protocol to be used while accessing the Portal Server. Possible values are http and https. 

PS_HOST

 

Fully Qualified Name of the Portal Server 

PS_PORT

 

Port number to be used for accessing the Portal Server. 

Table 14 Access Manager Information

Parameter 

Default Values 

Description 

PS_IDSAME_ADMIN_PASSWORD

Administrator (amadmin) Password 

 

The top level administrator (amadmin) password chosen during the Sun Java System Identity Server software installation. 

PS_IDSAME_LDAPUSER_PASSWORD

Internal LDAP Authentication User Password 

 

The Internal LDAP Authentication User Password chosen during the Sun Java System Identity Server installation. 

PS_DS_DIRMGR_DN

Directory Manager DN 

cn=Directory Manager

The directory manager DN chosen during the installation of the Sun Java System Directory Server. 

PS_DS_DIRMGR_PASSWORD

Directory Manager Password 

 

The directory manager Password chosen during the installation of the Sun Java System Directory Server. 

PS_DEPLOY_ADMIN_PASSWORD

Deploy Administrator Password 

 

This is the web-container’s Administrator Password. 

Table 15 Secure Remote Access Information

Parameter 

Default Values 

Description 

SRA_GW_PROTOCOL

Gateway Protocol 

https

The Protocol used by the gateway. The gateway will communicate using Secure Sockets Layer (SSL). 

SRA_GW_PORT

Gateway Port 

443

The port on which the gateway listens. 

SRA_GATEWAY_PROFILE

Gateway Profile Name 

default

A gateway profile contains all the information related to gateway configuration, such as the port on which gateway listens, SSL options, and proxy options. You can create multiple profiles in the gateway administration console and associate different instances of gateway with different profiles. 

See “Creating a Gateway Profile” in the Sun Java System Portal Server, Secure Remote Access 6 2005Q4 Administrator’s Guide. 

SRA_SERVER_DOMAIN

portal-server-domain-name

The domain name for the machine on which the Portal Server is installed. 

SRA_GW_DOMAIN

Gateway Domain 

gateway-domain-name

The domain name of the gateway machine. 

SRA_IDSAME_ADMIN_PASSWORD

Administrator (amadmin) Password 

 

The top level administrator (amadmin) password chosen during the Sun Java System Identity Server software installation. 

SRA_IDSAME_LDAPUSER_PASSWORD

Internal LDAP Authentication User Password 

 

The Internal LDAP Authentication User Password chosen during the Sun Java System Identity Server installation. 

SRA_DS_DIRMGR_DN

Directory Manager DN 

cn=Directory Manager

The directory manager DN chosen during the installation of the Sun Java System Directory Server. 

SRA_DS_DIRMGR_PASSWORD

Directory Manager Password 

 

The directory manager Password chosen during the installation of the Sun Java System Directory Server. 

SRA_DEPLOY_ADMIN_PASSWORD

Deploy Administrator Password 

 

This is the web-container’s Administrator Password. 

SRA_LOG_USER_PASSWORD

Gateway Logging User Password 

 

This allows administrators with non-root access to look at gateway log files. 

The sample silent file looks like the following:

################################################################################

#

# Install/Config components (Use comma (,) to separate entries ):

#

# 1. PortalServer

# 2. Secure Remote Access Core

# 3. Gateway

# 4. NetletProxy

# 5. RewriterProxy

#

################################################################################

COMPONENTS=1,2,3,4,5

BASEDIR=/opt

################################################################################

# Portal Server keys

################################################################################

##################### PS_CONFIGURATION_MODE possible values

####################

#

# configure - Configure the Portal Server Components.

# scrubds - Remove the Portal Server Components entries from the Directory Server.

# unconfigurewithoutscrubds - Unconfigure the Portal Server Components without removing the entries from the Directory Server.

# unconfigurewithscrubds - Unconfigure the Portal Server and also remove the entries from the Directory Server.

#

################################################################################

PS_CONFIGURATION_MODE=configure

##################### PS_DEPLOY_TYPE possible values###########################

#

# IWS = WebServer

# SUNONE = AppServer 7

# SUNONE8 = AppServer8.1

# WEBLOGIC = BEA WebLogic

# WEBSPHERE = IBM WebSphere

#

################################################################################

PS_DEPLOY_TYPE=SUNONE8

##################### PS_DEPLOY_DIR possible values############################

#

# /opt/SUNWwbsvr = WebServer

# /opt/SUNWappserver7 = AppServer 7

# /opt/SUNWappserver/appserver = AppServer 8.1

# /usr/local/bea = BEA WebLogic

# /opt/WebSphere/AppServer = IBM WebSphere

#

################################################################################

PS_DEPLOY_DIR=/opt/SUNWappserver/appserver

##################### PS_DEPLOY_DOMAIN possible values#########################

#

# null = WebServer

# /var/opt/SUNWappserver7/domains/domain1 = AppServer 7.0

# domain1 = AppServer 8.1

# mydomain = BEA WebLogic

# null = IBM WebSphere

#

################################################################################

PS_DEPLOY_DOMAIN=domain1

#################### PS_DEPLOY_INSTANCE_DIR possible values########################

#

# /var/opt/SUNWappserver/domains/domain1 = AppServer8.1

# null - for other containers.

#

################################################################################

PS_DEPLOY_INSTANCE_DIR=/var/opt/SUNWappserver/domains/domain1

##################### PS_DEPLOY_INSTANCE possible values#######################

#

# myportalbox.mydomain.com = WebServer

# server1 = AppServer 7.0

# server = AppServer 8.1

# myserver = BEA WebLogic

# server1 = IBM WebSphere

#

################################################################################

PS_DEPLOY_INSTANCE=server

##################### PS_DEPLOY_DOCROOT possible values#########################

#

# /opt/SUNWwbsvr/docs = WebServer

# /var/opt/SUNWappserver7/domains/domain1/server1/docroot = AppServer 7.0

# /var/opt/SUNWappserver/domains/domain1/docroot = AppServer 8.1

# /usr/local/bea/user_projects/domains/mydomain/applications = BEA WebLogic

# /opt/IBMHttpd/docs = IBM WebSphere

#

################################################################################

PS_DEPLOY_DOCROOT=/var/opt/SUNWappserver/domains/domain1/docroot

PS_DEPLOY_ADMIN=admin

PS_DEPLOY_ADMIN_PROTOCOL=https

PS_DEPLOY_ADMIN_HOST=myportalbox.mydomain.com

PS_DEPLOY_ADMIN_PORT=4848

####################### PS_DEPLOY_JDK_DIR possible values########################

#

#/usr/local/bea/jdk141_03 = BEA WebLogic (Please change this to your weblogic JDK Dir in your setup)

#/usr/jdk/entsys-j2se = for other containers.

#

###################################################################################

PS_DEPLOY_JDK_DIR=/usr/jdk/entsys-j2se

###################### PS_DEPLOY_PRODUCT_DIR possible values####################

#

# /usr/local/bea/weblogic81 = BEA WebLogic

# null - for other containers.

#

################################################################################

PS_DEPLOY_PRODUCT_DIR=null

#################### PS_DEPLOY_PROJECT_DIR possible values####################

#

# user_projects = BEA WebLogic

# null - for other containers.

#

################################################################################

PS_DEPLOY_PROJECT_DIR=null

######################## PS_DEPLOY_DOMAINS_DIR possible values###############

#

# domains = BEA WebLogic

# null - for other containers.

#

################################################################################

PS_DEPLOY_DOMAINS_DIR=null

################## PS_WEBLOGIC_CONFIG_DIR possible values#####################

#

# /usr/local/bea/user_projects/domains/mydomain = BEA WebLogic

# null - for other containers.

#

################################################################################

PS_WEBLOGIC_CONFIG_DIR=null

##################### PS_DEPLOY_NODE possible values##########################

#

# myportalbox = IBM WebSphere

# null - for other containers.

#

################################################################################

PS_DEPLOY_NODE=null

##################### PS_DEPLOY_CELL possible values##########################

#

# myportalbox = IBM WebSphere

# null - for other containers.

#

################################################################################

PS_DEPLOY_CELL=null

#################### PS_DEPLOY_VIRTUAL_HOST possible values##################

#

# default_host = IBM WebSphere

# null - for other containers.

#

################################################################################

PS_DEPLOY_VIRTUAL_HOST=null

PS_DEPLOY_URI=/portal

PS_LOAD_BALANCER_URL=http://myportalbox.mydomain.com:80/portal

PS_PROTOCOL=http

PS_HOST=myportalbox.mydomain.com

PS_PORT=80

PS_IDSAME_ADMIN_PASSWORD=admin123

PS_IDSAME_LDAPUSER_PASSWORD=test1234

PS_DS_DIRMGR_DN=cn=Directory Manager

PS_DS_DIRMGR_PASSWORD=admin123

PS_DEPLOY_ADMIN_PASSWORD=admin123

################################################################################

# SRACore keys

################################################################################

SRA_GW_PROTOCOL=http

SRA_GW_PORT=443

SRA_GATEWAY_PROFILE=default

SRA_SERVER_DOMAIN=mydomain.com

SRA_GW_DOMAIN=mydomain.com

SRA_IDSAME_ADMIN_PASSWORD=admin123

SRA_IDSAME_LDAPUSER_PASSWORD=test1234

SRA_DS_DIRMGR_DN=cn=Directory Manager

SRA_DS_DIRMGR_PASSWORD=admin123

SRA_DEPLOY_ADMIN_PASSWORD=admin123

SRA_LOG_USER_PASSWORD=admin123

################################################################################

# Gateway keys

################################################################################

GW_PROTOCOL=https

GW_HOST=mygwbox.mydomain.com

GW_PORT=443

GW_IP=129.158.227.209

GW_GATEWAY_PROFILE=default

GW_LOAD_BALANCER_URL=http://mygwbox.mydomain.com:80/portal

GW_CERT_INFO=”CN=$GW_HOST,L=Santa

Clara,ST=California,C=us,O=Portal,OU=Sun”

GW_SRA_LOG_USER_PASSWORD=admin123

GW_CERT_DB_PASSWORD=admin123

################################################################################

Gateway Configuration Checklist

Gateway Configuration Checklist is a three column table for the Gateway Installation Checklist.

Table 16 Gateway Configuration Checklist

Parameter  

Default Value  

Description  

GW_PROTOCOL

https

The protocol used by the gateway. The gateway will usually communicate using Secure Sockets Layer (SSL). 

GW_HOST

mygwbox.mydomain.com 

The host name of the machine on which the gateway is installed. 

GW_PORT

443

The port on which the gateway machine listens. 

GW_IP

gw-host-ip-address

The IP Address should be that of the machine where Gateway is installed and not that of the Sun Java System Identity Server. 

GW_GATEWAY_PROFILE

Gateway Profile Name 

default

A gateway profile contains all the information related to gateway configuration, such as the port on which gateway listens, SSL options, and proxy options. You can create multiple profiles in the gateway administration console and associate different instances of gateway with different profiles. See “Creating a Gateway Profile” in the Sun Java System Portal Server, Secure Remote Access 6 2005Q1 Administrator’s Guide.

GW_LOAD_BALANCER_URL

Load balancer controlling Portal Server Instances. 

 

If you are not using any Load Balancer URL then use the Portal Server URL. http://fully-qualified-domain:port/portal-deploy-uri for example: http://myportalbox.mydomain.com:80/portal

GW_CERT_INFO

 

The Certificate Information should be provided in the following format: 

“CN=$GW_HOST,L=The name of your city or locality,ST=The name of your state,C=The two letter country code for your country,O=The name of your organization,OU=The name of your division”

For example, “CN=$GW_HOST,L=SantaClara,ST=California,C=us,O=Portal,OU=Sun” 

GW_SRA_LOG_USER_PASSWORD

Gateway Logging User Password 

 

This allows administrators with non-root access to look at gateway log files. 

GW_CERT_DB_PASSWORD

Certificate Database Password 

 

This can be any password you choose. 

Certificate Information 

Organization (O) 

MyOrganization 

The name of your organization. 

Division (OU) 

MyDivision 

The name of your division. 

City or Locality (L) 

MyCity 

The name of your city or locality 

State or Province (ST) 

MyState 

The name of your state 

Two-Letter Country Code (C) 

us 

The two letter country code for your country. 

Certificate Database Password 

 

This can be any password you choose. 

Retype Password 

 

Retype the password to verify. 

Netlet Proxy Configuration Checklist

Netlet Proxy Configuration Checklist is a three column table for the Netlet Proxy Installation Checklist. The first column lists the parameters. The second column lists the default value. The third column lists a description for the parameter.

Table 17 Netlet Proxy Configuration Checklist

Parameter 

Default Value  

Description  

NLP_PROTOCOL

https

The protocol used by the Netlet Proxy. The Netlet Proxy will usually communicate using Secure Sockets Layer (SSL). 

NLP_HOST

myportalbox.mydomain.com 

The host name of the machine on which Netlet Proxy is installed. 

NLP_PORT

10555

The port on which the Netlet Proxy listens. 

NLP_IP

host-ip-address

The IP address should be that of the machine where Netlet Proxy is installed and not that of Sun Java System Identity Server. 

NLP_GATEWAY_PROFILE

Gateway Profile Name 

default

Specify the same profile name specified when you installed Portal Server or Secure Remote Access support. 

See “Creating a Gateway Profile” in the Sun java System Portal Server, Secure Remote Access 6 2005Q1 Administrator’s Guide for more information. 

NLP_LOAD_BALANCER_URL

Load balancer controlling Portal Server Instances. 

 

If you are not using any Load Balancer URL then use the Portal Server URL. http://fully-qualified-domain:port/portal-deploy-uri

For example http://myportalbox.mydomain.com:80/portal

NLP_CERT_INFO

 

The Certificate Information should be mentioned in the following format “CN=$GW_HOST, L=<The name of your city or locality>,ST=<The name of your state>,C=<The two letter country code for your country>,O=<The name of your organization>,OU=<The name of your division>” 

For example, “CN=$GW_HOST,L=SantaClara,ST=California,C=us,O=Portal,OU=Sun” 

NLP_SRA_LOG_USER_PASSWORD

Gateway Logging User Password 

 

This allows administrators with non-root access to look at gateway log files. 

Rewriter Proxy Configuration Checklist

Rewriter Proxy Configuration Checklist is a three column table for the Rewriter Proxy Installation Checklist. The first column lists the parameters. The second column lists the default value. The third column lists a description for the parameter.

Table 18 Rewriter Proxy Checklist

Parameter 

Default Value  

Description  

RWP_PROTOCOL

https

The protocol used by the Rewriter Proxy. The Rewriter Proxy will usually communicate using Secure Sockets Layer (SSL). 

RWP_HOST

myportalbox.mydomain.com 

The host name of the machine on which Rewriter Proxy is installed. 

RWP_PORT

10443

The port on which the Rewriter Proxy listens. 

RWP_IP

host-ip-address

The IP address should be that of the machine where Rewriter Proxy is installed and not that of Sun Java System Identity Server. 

RWP_GATEWAY_PROFILE

Gateway Profile Name 

default

Specify the same profile name specified when you installed Portal Server or Secure Remote Access support. See “Creating a Gateway Profile” in the Sun java System Portal Server, Secure Remote Access 6 2005Q1 Administrator’s Guide for more information. 

RWP_LOAD_BALANCER_URL

Load balancer controlling Portal Server Instances. 

 

If you are not using any Load Balancer URL then use the Portal Server URL. http://fully-qualified-domain:port/portal-deploy-uri for example http://myportalbox.mydomain.com:80/portal

RWP_CERT_INFO

 

The Certificate Information should be provided in the following format “CN=$GW_HOST,L=<The name of your city or locality>,ST=<The name of your state>,C=<The two letter country code for your country>,O=<The name of your organization>,OU=<The name of your division>” 

For example “CN=$GW_HOST,L=SantaClara,ST=California,C=us,O=Portal,OU=Sun” 

RWP_SRA_LOG_USER_PASSWORD

Gateway Logging User Password 

 

This allows administrators with non-root access to look at gateway log files. 

Configuring Portal Server in Interactive Mode

ProcedureTo Use the psconfig script For Configuring Portal Server in Interactive Mode

Steps

  1. As root in a terminal window, go to the directory that contains the psconfig script:

    cd PortalServer-base/lib

  2. To configure Portal Server in interactive mode, execute the psconfig script by typing ./psconfig and then enter appropriate answers for the configuration questions.

Portal Server

The Portal Server checklists are three column tables that list all the values that you might need for a post-minimal install configuration. Depending on the type of installation you perform, the values that you use might vary.

The following tables are three column tables that list the values that you might need for a post minimal-install configuration. Depending on the type of installation you perform, the values that you use might vary. The tables list the information for:

Table 19 Component Selection

Question 

Default Value 

Description  

Select the component(s) for Installation or Uninstallation: 

1. Portal Server 

2. Secure Remote Access Core 

3. Gateway 

4. Netlet Proxy 

5. Rewriter Proxy 

1 

  • Set “1” to configure PortalServer.

  • Set “2” to configureSecure Remote Access Core.

  • Set “3” to configure Gateway.

  • Set “4” to configure NetletProxy.

  • Set “5” to configure RewriterProxy.

    To Configure multiple components, Use comma (,) to separate entries.

Table 20 Configuration Mode

Question 

Default Value 

Description 

Choose one of the following configuration options: 

1. configure 

2. scrubds 

3. unconfigurewithoutscrubds 

4. unconfigurewithscrubds 

configure 

configure– Configure the Portal Server Components. 

scrubds– Remove the Portal Server Components entries from the Directory Server. 

unconfigurewithoutscrubds– Unconfigure the Portal Server Components without removing the entries from the Directory Server. 

unconfigurewithscrubds– Unconfigure the Portal Server and also remove the entries from the Directory Server. 

Table 21 Portal Server Configuration Information

Question 

Default Value 

Description 

What is the Portal Server Web Containers host 

myportalbox.mydomain 

.com 

Fully Qualified Name of the Portal Server 

Is the Portal Server Web Containers port secure 

No 

The Protocol to be used while accessing the Portal Server. Possible values are No : If the Protocol is http. Or Yes: If the Protocol is https 

What is the Portal Server Web Containers port 

80 

Port number to be used for accessing the Portal Server. 

What is the Portal Server deployment URI 

/portal

The URI is the space on the web server or application server that the Portal Server uses. The value for the deployment URI must have a leading slash and must contain only one slash. However, the deployment URI can not be a “/" by itself. 

Choose the container to which the portalserver needs to be configured: 

1. Sun Java System Web Server Table 22

2. Sun Java System Application Server 8.1 Table 23

3. Sun Java System Application Server 7.0 Table 24

4. BEA WebLogic Application Server Table 25

5. IBM Websphere Application Server Table 26

1 

The web container on which Portal Server is being deployed. Possible values are 

1 = Sun Java System Web Server 

2 = Sun Java System Application Server 7.0 

3 = Sun Java System Application Server 8.1 

4 = BEA WebLogic Server 8.1 SP2 

5= IBM WebSphere Application Server 

Table 22 Sun Java System Web Server

Question 

Default Value 

Description 

Where is the Web Container installed 

/opt/SUNWwbsvr

Directory in which the Sun Java System Web Server is installed. 

What is the Web Container instance 

myportalbox 

.mydomain 

.com 

The web server instance you want the Portal Server to use. Note: The instance name should not contain spaces. 

Table 23 Sun Java System Application Server 7.0

Question 

Default Value 

Description 

Where is the Web Container installed 

/opt/SUNWappserver7

Directory in which the Sun Java System Application Server 7.0 is installed 

What is the Web Container domain 

/var/opt/SUNWappserver7/domains/domain1

The Sun Java System Application Server domain contains a set of instances. The domain specified will contain the instance used by the Portal Server. This domain must already be configured. 

What is the Web Container administrator 

admin 

The administrator user ID. 

What is the Web Container administration port 

4848 

The port number of the administration server. 

Is the Web Container administration port secure 

No 

The Protocol to be used while accessing the Portal Server. Possible values are 

No : If the Protocol is http 

Yes: If the Protocol is https 

What is the Web Container instance 

server1 

The name of the Sun Java System Application Server instance to which the Portal Server will be deployed. This instance must already be configured. The instance name should not contain spaces. 

What is the Web Container document root directory 

/var/opt/SUNWappserver7/domains/domain1/server1/docroot

The Application Server Directory where static pages are kept. 

What is the Web Container administrator password 

 

This is the web-container’s Administrator Password. 

Table 24 Sun Java System Application Server 8.1

Question 

Default Value 

Description 

Where is the Web Container installed 

/opt/SUNWappserver/appserver

Directory in which the Sun Java System Application Server 8.1 is installed 

What is the Web Container domain 

domain1 

The Sun Java System Application Server domain contains a set of instances. The domain specified will contain the instance used by the Portal Server. This domain must already be configured. 

What is the Web Container Deploy Instance Dir 

/var/opt/SUNWappserver/domains/domain1

The full path of the domain specified that will be configured for the Portal Server. 

What is the Web Container Deploy Instance 

server 

The name of the Sun Java System Application Server instance to which the Portal Server will be deployed. This instance must already be configured. The instance name should not contain spaces. 

What is the Web Container Document Directory 

/var/opt/SUNWappserver/domains/domain1/docroot

The Application Server Directory where static pages are kept. 

Who is the Web Container administrator 

admin 

The administrator user ID. 

What is the HostName of the Machine where Web Container is Installed 

myportalbox.mydomain.com 

The administration server hostname. 

Is the Web Container administration port secure 

Yes 

The Protocol to be used while accessing the Portal Server. Possible values are No If the Protocol is http Or Yes If the Protocol is https. 

What is the Web Container administration port 

4849 

The port number of the administration server. Note: The default Administrator Port for Sun Java System Application Sever 8.1 is “4849.” 

What is the Web Container administrator password 

 

This is the web-container’s Administrator Password. 

Table 25 BEA WebLogic Server

Question 

Default Value 

Description 

Where is the Web Container Home Directory 

/usr/local/bea

The directory in which BEA is installed. 

Where is the Web Container Product Directory 

/usr/local/bea/weblogic81

The directory in which the BEA WebLogic Server software is installed. 

What is the Web Container domain 

mydomain 

The BEA WebLogic Server domain contains a set of instances. The domain specified will contain the instance used by the Portal Server. This domain must already be configured. 

What is the Web Container administrator 

weblogic 

The administrator user ID. 

What is the HostName of the Machine where Web Container is Installed 

myportalbox.mydomain.com 

The Portal server hostname. 

What is the Web Container administration port 

7001 

The port number of the administration server. 

Is the Web Container administration port secure 

No 

The administration server Protocol. 

No : If the Protocol is http 

Yes: If the Protocol is https. 

What is the User Projects Directory 

user_projects

This is the user project’s directory. Use the value you entered during BEA WebLogic installation. 

What is the Deploy Domains Directory 

domains

The name of the directory containing the BEA WebLogic Server domain. 

What is the Web Container Configuration Directory Location 

/usr/local/bea/user_projects/domains/mydomain

The full path of the BEA WebLogic Server domain 

What is the Web Container instance 

myserver 

The name of the BEA WebLogic Server instance to which the Portal Server will be deployed. This instance must already be configured. The name must not contain a space. If you are installing Portal Server on an administration server instance this will be the name of the administration server instance. Otherwise it will be the name of the managed server instance. 

What is the Web Container document root directory 

/usr/local/bea/user_projects/domains/mydomain/applications

The document root value of DefaultWebApp needs to be deployed to the BEA WebLogic Server instance you are running the Portal Server software on. DefaultWebApp is the default web application, from which static content is served in a BEA WebLogic Server. By default it is only deployed to the domain (mydomain) and the server instance defined or created during the BEA WebLogic Server install. 

If you create your own BEA WebLogic Server or domain, you need to deploy the DefaultWebApp to it, either by copying the directory to the new server’s deployment directory, or by using the BEA WebLogic Server administration console. 

See the BEA WebLogic Server documentation for more detail on how to configure a default web application. 

What is the Web Container JDK Home 

/usr/local/bea/jdk141_03

The JDK Dir that is being used by the BEA WebLogic server. 

What is the Web Container administrator password 

 

This is the web-container’s Administrator Password. 

Again 

 

Re-enter the web-container’s Administrator Password. 

Table 26 IBM WebSphere Application Server

Question 

Default Value 

Description 

Where is the Web Container installed 

/opt/WebSphere/Express51/AppServer

The directory in which the IBM WebSphere Application Server software is installed. 

What is the Virtual Host Name 

default_host 

Use the value you entered during IBM WebSphere installation. 

What is the Node name 

myportalbox 

 

What is the Cell name 

myportalbox 

 

Instance nickname 

server1 

The name of the instance to which the Portal Server will be deployed. This instance must already be configured. Portal Server can not be installed into an application server instance or domain whose name contains a dash or a space, for example, Default-Server or Default Server. 

What is the Web Container document root directory 

/opt/IBMHTTPD/htdocs/en_US

The directory where static pages are kept. This directory is created during the Sun Java System Identity Server installation. 

What is the Web Container JDK Home 

/usr/jdk/entsys-j2se

The JDK directory that is being used by the we container. 

Table 27 Load Balancer Information

Question 

Default Value 

Description 

PS_LOAD_BALANCER_URL Load balancer controlling Portal Server Instances 

http://myportalbox.mydomain.com:80/portal

If you are not using any Load Balancer URL then use the Portal Server URL. http://fully-qualified-domain:port/portal-deploy-uri

For example 

http://myportalbox.mydomain.com:80/portal

Table 28 Access Manager Information

Question 

Default Value 

Description 

What is the Access Manager Administrator (amadmin) Password 

Administrator (amadmin) Password 

 

The top level administrator (amadmin) password chosen during the Sun Java System Identity Server software installation. 

Again 

 

Re-enter the top level administrator (amadmin) password. 

What is the Access Manager Internal LDAP Authentication User Password 

Internal LDAP Authentication User Password 

 

The Internal LDAP Authentication User Password chosen during the Sun Java System Identity Server installation. 

Again 

 

Re-enter the Internal LDAP Authentication User Password. 

What is the Directory Manager DN 

Directory Manager DN 

cn=Directory Manager 

The directory manager DN chosen during the installation of the Sun Java System Directory Server. 

What is the Directory Manager Password 

Directory Manager Password 

 

The Directory Manager Password chosen during the installation of the Sun Java System Directory Server. 

Again 

 

Re-enter the Directory Manager Password. 

PS_DEPLOY_ADMIN_PASSWORD 

Deploy AdministratorPassword 

 

This is the web-container’s Administrator Password. 

Table 29 Secure Remote Access Core Configuration Information

Question 

Default Value 

Description 

What is the Gateway protocol 

Gateway Protocol 

https 

The Protocol used by the gateway. The gateway will communicate using Secure Sockets Layer (SSL). 

What is the Portal Server domain 

Portal Server Domain 

portal-server-domain-name

The domain name for the machine on which the Portal Server is installed. 

What is the Gateway domain 

Gateway Domain 

gateway-domain-name

The domain name of the gateway machine. 

What is the Gateway port 

Gateway Port 

443 

The port on which the gateway listens. 

What is the Gateway profile 

Gateway Profile Name 

default 

A gateway profile contains all the information related to gateway configuration, such as the port on which gateway listens, SSL options, and proxy options. 

You can create multiple profiles in the gateway administration console and associate different instances of gateway with different profiles. 

See “Creating a Gateway Profile” in the Sun Java System Portal Server, Secure Remote Access 6 2005Q1 Administrator’s Guide. 

What is the Gateway logging user password 

Gateway Logging User Password 

 

This allows administrators with non-root access to look at gateway log files. 

Again 

 

Re-enter the Gateway Logging User Password. 

Gateway

The Gateway Configuration Checklist is a three column table that contains the checklist for gateway configuration. Column one lists the parameter. Column two contains the default value for the parameter. Column three lists the description.

Table 30 Gateway Configuration Checklist

Question  

Default Value  

Description  

What is the Gateway protocol 

https 

The protocol used by the gateway. The gateway will usually communicate using Secure Sockets Layer (SSL). 

What is the Gateway host 

mygwbox.mydomain.com 

The host name of the machine on which the gateway is installed. 

What is the Gateway port 

443 

The port on which the gateway machine listens. 

What is the Gateway IP Address 

gw-host-ip-address

The IP Address should be that of the machine where Gateway is installed and not that of the Sun Java System Identity Server. 

What is the Gateway profile Gateway Profile Name 

default 

A gateway profile contains all the information related to gateway configuration, such as the port on which gateway listens, SSL options, and proxy options. 

You can create multiple profiles in the gateway administration console and associate different instances of gateway with different profiles. 

See “Creating a Gateway Profile” in the Sun Java System Portal Server, Secure Remote Access 6 2005Q4 Administrator’s Guide.

What is the Gateway logging user password 

Gateway Logging User Password 

 

This allows administrators with non-root access to look at gateway log files. 

Again 

 

Re-enter the Gateway Logging User Password. 

What is the Portal Server Load Balancer URL 

Load balancer controlling Portal Server Instances. 

 

If you are not using any Load Balancer URL then use the Portal Server URL. http://fully-qualified-domain:port/portal-deploy-uri

For example, http://myportalbox.mydomain.com:80/portal

Certificate Information 

What is the name of your organization 

MyOrganization 

The name of your organization. 

What is the name of your division 

MyDivision 

The name of your division. 

What is the name of your city or locality 

MyCity 

The name of your city or locality 

What is the name of your state or province 

MyState 

The name of your state 

What is the two-letter country code 

us 

The two letter country code for your country. 

What is the password for the Certificate Database 

 

This can be any password you choose. 

Again 

 

Retype the Certificate Database password to verify. 

Netlet Proxy

The Netlet Proxy Configuration Checklist is a three column table for the Netlet Proxy configuration checklist. Column one lists the parameter. Column two lists the default value. Column three contains the description.

Table 31 Netlet Proxy Configuration Checklist

Question 

Default Value  

Description  

What is the Netlet Proxy protocol 

https 

The protocol used by the Netlet Proxy. The Netlet Proxy will usually communicate using Secure Sockets Layer (SSL). 

What is the Netlet Proxy host 

myportalbox.mydomain.com 

The host name of the machine on which Netlet Proxy is installed. 

What is the Netlet Proxy port 

10555 

The port on which the Netlet Proxy listens. 

What is the Netlet Proxy IP Address 

host-ip-address

The IP address should be that of the machine where Netlet Proxy is installed and not that of Sun Java System Identity Server. 

What is the Gateway profile 

Gateway Profile Name 

default 

Specify the same profile name specified when you installed Portal Server or Secure Remote Access support. 

See “Creating a Gateway Profile” in the Sun Java System Portal Server, Secure Remote Access 6 2005Q1 Administrator’s Guide for more information.

What is the Gateway logging user password 

Gateway Logging User Password 

 

This allows administrators with non-root access to look at gateway log files. 

Again 

 

Re-enter the Gateway Logging User Password. 

What is the Portal Server Load Balancer URL 

Load balancer controlling Portal Server Instances. 

 

If you are not using any Load Balancer URL then use the Portal Server URL. http://fully-qualified-domain:port/portal-deploy-uri

For example http://myportalbox.mydomain.com:80/portal

Certificate Information 

What is the name of your organization 

MyOrganization 

The name of your organization. 

What is the name of your division 

MyDivision 

The name of your division. 

What is the name of your city or locality 

MyCity 

The name of your city or locality 

What is the name of your state or province 

MyState 

The name of your state 

What is the two-letter country code 

us 

The two letter country code for your country. 

What is the password for the Certificate Database 

 

This can be any password you choose. 

Again 

 

Retype the Certificate Database password to verify. 

Rewriter Proxy

The Rewriter Proxy Configuration Checklist is a three column table that contains the Rewriter Proxy configuration checklist. Column one lists the parameter. Column two lists the default value. Column three contains the description.

Table 32 Rewriter Proxy Configuration Checklist

Question 

Default Value 

Description  

What is the Rewriter Proxy protocol 

https 

The protocol used by the Rewriter Proxy. The Rewriter Proxy will usually communicate using Secure Sockets Layer (SSL). 

What is the Rewriter Proxy host 

myportalbox.mydomain.com 

The host name of the machine on which Rewriter Proxy is installed. 

What is the Rewriter Proxy port 

10443 

The port on which the Rewriter Proxy listens. 

What is the Rewriter Proxy IP Address 

host-ip-address

The IP address should be that of the machine where Rewriter Proxy is installed and not that of Sun Java System Identity Server. 

What is the Gateway profile 

Gateway Profile Name 

default 

Specify the same profile name specified when you installed Portal Server or Secure Remote Access support. 

See “Creating a Gateway Profile” in the Sun Java System Portal Server, Secure Remote Access 6 2005Q1 Administrator’s Guide for more information.

What is the Gateway logging user password 

Gateway Logging User Password 

 

This allows administrators with non-root access to look at gateway log files. 

Again 

 

Re-enter the Gateway Logging User Password. 

What is the Portal Server Load Balancer URL 

Load balancer controlling Portal Server Instances. 

 

If you are not using any Load Balancer URL then use the Portal Server URL. http://fully-qualified-domain:port/portal-deploy-uri

For Example, http://myportalbox.mydomain.com:80/portal

Certificate Information 

What is the name of your organization 

MyOrganization 

The name of your organization. 

What is the name of your division 

MyDivision 

The name of your division. 

What is the name of your city or locality 

MyCity 

The name of your city or locality 

What is the name of your state or province 

MyState 

The name of your state 

What is the two-letter country code 

us 

The two letter country code for your country. 

What is the password for the Certificate Database 

 

This can be any password you choose. 

Again 

 

Retype the Certificate Database password to verify. 

For information on post-installation tasks see Portal Server Post-Installation Tasks.

Configuring Portal Server in Silent Mode

To configure the Portal Server using the samplesilent file, modify the pssamplesilent file located at PortalServer-baseSUNWps/lib and execute the psconfig script.

ProcedureTo Use the pssamplesilentfile for Configuring Portal Server in Silent Mode

Steps

  1. As root in a terminal window, go to the directory that contains the psconfig script:

    cd PortalServer-baseSUNWps/lib

  2. Type:

    ./psconfig -s pssamplesilentfile

    For information on post-installation tasks see Portal Server Post-Installation Tasks

Portal Server Post-Installation Tasks

Post-installation tasks need to be performed for each of the following components:

ProcedureTo Access Portal Server

Before You Begin

To access the Portal Server or the Identity Server administration console the directory server and the web container must first be started.

Step

    Use the following command to start a local installation of the directory server:

    /var/opt/mps/serverroot/slapd-hostname/start-slapd

    The following post-installation tasks depend on the type of web container on which you deployed the Portal Server.

    • Sun Java System Web Server

    • Sun Java System Application Server

    • BEA WebLogic Server

    • IBM WebSphere Application Server

ProcedureTo Start the Sun Java System Web Server

Steps

  1. Start the admin instance. In a terminal window type:


    cd WebServer-base/SUNWwbsrv/https-webserver-instance-name
./start

    or

  2. Access the Sun Java System Web Server administration console.

  3. Click Apply Changes to restart the web container.

ProcedureTo Start Sun Java System Application Server 7.0

Step

    In a terminal window, change directories to the application server’s instances utilities directory and run the startserv script. The following example assumes that the default application server domain and instance have been used.

    cd /var/opt/SUNWappserver7/domains/domain1/server1/bin
./startserv

    To stop and start the Sun Java System Application Server using the asadmin utility or from the Sun Java System Application Server administration console, consult the Sun Java System Application Server documentation.

ProcedureTo Configure the Sun Java System Application Server 8.1 Instance

Steps

  1. Stop the domain instance. In a terminal window, type:

    /opt/SUNWappserver/appserver/bin/asadmin stop-domain domainname

    For example

    /opt/SUNWappserver/appserver/bin/asadmin stop-domain domain1

  2. Start the domain instance. In a terminal window, type:

    /opt/SUNWappserver/appserver/bin/asadmin start-domain --user administrator-user-name --password administartor-user-password domainname

    For example,

    /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin --password password domain1

ProcedureTo Deploy Portal Server on BEA WebLogic Server

Before You Begin

Portal Server must be installed before performing the following steps.

Steps

  1. Check the /var/sadm/install/logs/Java_Enterprise_System_install.BMMddhhmm file for errors.

    MM = month

    dd = day

    hh = hour

    mm = minute

  2. Stop all BEA WebLogic Server instances (the admin and managed servers).

  3. Start the BEA WebLogic admin server instance. If you have installed on a managed instance, start the managed instance too.

  4. From the command line, execute the following:

    PortalServer-base/bin/deploy

    Choose the default for the deploy URI and server instance name, and enter the BEA WebLogic Server admin password when prompted.

  5. Restart the BEA WebLogic Server instance into which Portal Server was deployed.See your web container documentation for instructions on starting the web container instance.

    Note –

    In the case of a managed server installation, the .war files do not get deployed. The .war files should be deployed using the BEA WebLogic Server administration console.

    If you will be supporting multiple authentication methods, for example, LDAP, UNIX, Anonymous, you must add each authentication type to the Core authentication service to create an authentication menu. See the Sun Java System Portal Server 6 2005Q1 Administration Guide for further information.

ProcedureTo Deploy Portal Server on IBM WebSphere Application Server

Steps

  1. Check the /var/sadm/install/logs/Java_Enterprise_System_install.B/MMddhhmm file for errors.

  2. Stop and restart the application server instance and the application server node. See your web container documentation for instructions on starting the web container instance.

  3. From the command line, execute the following:

    PortalServer-base/bin/deploy

    Choose the default for the deploy URI and server instance name, and enter IBM WebSphere Server admin password when prompted.

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.

ProcedureTo 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

  1. Restart the BEA WebLogic 8.1 or IBM WebSphere Application Server 5.1 instance.

  2. 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.

  3. Make sure that the PATH setting includes /usr/bin. This is needed for awk part of script to run correctly.

  4. Execute the following commands to configure 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.

ProcedureTo 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

  1. Restart the Web Server or Application Server instance

  2. Make sure that the PATH setting includes /usr/bin. This is needed for awk part of script to run correctly.

  3. 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).

ProcedureConfiguring 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

  1. Log in to the Access Manager Administration Console.

  2. Select the Service Configuration tab.

  3. Click Gateway.

  4. Add the second Portal to the Forward Cookie URLs list.

ProcedureStarting and Stopping the Gateway

Steps

  1. 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:

  2. Add this package by running pkgadd -d . SUNWrhino from the current directory.

  3. 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.

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.

ProcedureTo Install the jCIFS Libraries

Steps

  1. Add this package by running pkgadd -d . SUNWjcifs from the current (this) directory.

  2. Run portal-server-install-base/SUNWps/lib/postinstall_JCIFS

  3. Run portal-server-install-base/SUNWps/bin/undeploy

  4. Run portal-server-install-base/SUNWps/bin/deploy command.

  5. Restart the server.

Verifying the Portal Server Installation

Access the Portal Server Administration Console and Desktop

ProcedureTo Access the Sun Java System Identity Server Administration Console

Steps

  1. Open a browser.

  2. Type protocol://hostname.domain:port/amconsole

    For example,

    http://example.com:80/amconsole

  3. Enter the administrator’s name and password to view the administration console.

    This is the name and password you specified at the time of installing the Sun Java System Identity Server software.

To Access the Portal Server Desktop

Verify the Portal Server installation by accessing the Desktop. Use the following URL to access the Desktop: protocol://fully-qualified-hostname:port/portal-URI

For example,

http://example.com:80/portal

When you access the Desktop, the Authless Desktop is displayed. This allows users accessing the Desktop URL to be authenticated automatically and granted access to the Desktop.

If the sample Portal Desktop displays without any exception, then your Portal Server installation is good.

ProcedureVerifying the Gateway Installation

Steps

  1. Run the following command to check if the gateway is running on the specified port (the default port is 443):

    netstat -an | grep port-number

    If the gateway is not running, start the gateway in the debug mode, and view messages that are printed on the console. Use the following command to start the gateway in debug mode:

    PortalServer-base/bin/gateway -n profilename start debug

    Also view the log files after setting the gateway.debug attribute in the platform.conf.profilename file to message. See the section Understanding the platform.conf File in Chapter 2, “Administering Gateway” in the Sun Java System Portal Server, Secure Remote Access 6 2005Q1 Administration Guide, for details.

  2. Run the Portal Server in secure mode by typing the gateway URL in your browser:

    https://gateway-machine-name:portnumber

    If you have chosen the default port (443) during installation, you need not specify the port number.

  3. Login to the Identity Server administration console as administrator using the user name amadmin, and using the password specified during installation.

    You can now create new organizations, roles, and users and assign required services and attributes in the administration console.