test

Sun Java System Portal Server 6 2005Q4 Release Notes

Sun JavaTM System Portal Server Release Notes

These Release Notes contain important information available at the time of release of Sun Java System Portal Server 6 2005Q4. New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Portal Server 6 2005Q4.

The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: http://docs.sun.com/. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and product documentation.

These release notes contain the following sections:

Third-party URLs may be referenced in this document and provide additional, related information.

Note –

Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Release Notes Revision History

Table 1 Revision History

Date  

Description of Changes  

September 10, 2005 

Final Release of Sun Java System Portal Server 6 2005Q4 Release Notes.

September 19, 2005 

Update to Final Release of Sun Java System Portal Server 6 2005Q4 Release Notes.

September 29, 2005 

Added bugs in “Known Issues and Limitations for the Sun Java Enterprise System 4 Release.” 

November 15, 2005 

Fixed errors in tables. 

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.

Important Information

This section contains the latest information that is not contained in the core product documentation. This section covers the following topics:

Installation Notes

Portal Server

Portal Server can be installed and configured to run with either:

ProcedureTo Run the Liberty Samples On A Portal Server/Access Manager Separated Install

Steps

  1. Make sure the SP_HOST_DOMAIN value in configSP.sh points to the Access Manager full install host.

  2. In the administration console of Access Manager that is acting as Service Provider, set the Provider Home Page to URL=http://portal-server-host:port/portal/dt

    To set this value:

    1. Select the federation management tab.

    2. Select the service provider in navigation frame.

    3. Select provider in the drop-down in data frame.

    4. Scroll down to Access Manager Configuration section.

    5. Set the Provider Home Page to URL=http:// portal-server-host : port /portal/dt.

      For Liberty Sample 3 only, perform step 3 and step 4.

  3. Change “Single Sign-On Failure Redirect URL” and set it to http://portal-server-host:port/portal/dt?libertySSOFailed=true

    To set this value:

    1. Select the federation management tab.

    2. Select the service provider in navigation frame.

    3. Select provider in the drop-down in data frame.

    4. Scroll down to Access Manager Configuration section.

    5. Set the Single Sign-On Failure Redirect URL to http:// portal-server-host : port /portal/dt?libertySSOFailed=true

  4. Set the PreLogin URL to http://portal-server-host:identity-server-port/amserver/preLogin?metaAlias=is-host&goto=http://portal-server-host:portal-server-port/portal/dt

    To set this value:

    1. Go to Identity Management, Select Users from the drop down Menu.

    2. Click on authlessanonymous user and then select Portal Desktop from the View drop down list in the Navigation Frame.

    3. Click on the Edit link.

    4. Click on Manage Channels and Containers.

    5. Click on Edit properties of the Login Channel.

    6. Set the PreLogin URL to http:// portal-server-host : identity-server-port /amserver/preLogin?metaAlias=is-host&goto=http:// portal-server-host : portal-server-port /portal/dt.

  5. Set the following in the AMConfig.properties file on the Portal Server host:

    • com.iplanet.am.notification.url=http://portal-server-host:port/servlet/com.iplanet.services.comm.client.PLLNotificationServlet

    • com.iplanet.am.session.client.polling.enable=false

Web Containers

For detailed instructions on installing the Sun Java Server component products, refer to the Sun Java Enterprise System Installation Guide at http://docs.sun.com/db/doc/819-0056

Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at: http://sun.com/software/javaenterprisesystem/get.html.

For information on Sun's commitment to accessibility, visit http://sun.com/access.

Compatibility Issues

Communication Channels

The Server and Port properties are missing for configuring the properties of the Instant Messaging (IM) channel. Because all communication happens with the multiplexor, the server and port settings have been removed from the provider. This is an incompatibity between the Java System Enterprise 2 and Java Enterprise System 4 release.

Deprecation Notifications and Announcements

This section contains information about features that will not be supported in a future release.

Operating System and Required Component Software

Support for the following operating system platforms and application server are being deprecated and will not be supported in future releases:

Portal Server CLIs

Existing Portal Server command line utilities are deprecated, and their functions will be replaced with a single Portal Server command line utility in a future release. The following Portal Server command line utilities are deprecated, and their functions will be replaced with a single Portal Server command line utility in a future release:

Administration Console

The existing Portal Server administration console is deprecated, and its functions will be replaced with a new Portal Server management console in a future release.

Portal Server Desktop Template Container Provider

The Portal Desktop Template Container Provider interface is being deprecated and will be removed in a future release. Interface components being deprecated include:

Installation Issues

When you run the Java Enterprise System Installer, Access Manager 7 2005Q4 has two installation types (or modes):

If you are installing Access Manager with any of the following products, you must select Legacy (6.x) mode:

For more information, see the Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.

Documentation Updates for Portal Server 6 2005Q4

The following sections provide updates and additional documentation for the Portal Server 6 2005Q4 documentation set.

Portal Server Administration Guide

Instant Messaging Updates

The settings on the Instant Messaging Channel edit page have changed. The Desktop user now has to configure only two settings (if the administrator has not configured the channel for a single Instant Messaging Server).

The two Instant Messaging Server settings are now:

Performance and Tuning Updates

The perftune script has been changed. The amtune script is now used. Use the follow the steps to use the performance tuning tools.

Note –

In each step substitute your actual base path if you did not choose the default during installation.

  1. Edit /opt/SUNWam/bin/amtune/amtune-as8 as follows. Find the line: $ECHO $ASADMIN_PASSWORD > $ASADMIN_PASSFILE and change it to: $ECHO "AS_ADMIN_PASSWORD=$ASADMIN_PASSWORD" > $ASADMIN_PASSFILE

  2. Edit /opt/SUNWam/bin/amtune/amtune-env as follows. Find the line: ASADMIN=$CONTAINER_BASE_DIR/bin/asadmin and change it to: ASADMIN=/opt/SUNWappserver/appserver/bin/asadminThe, basedir /opt, may be different for you. Verify that asadmin is actually at the location you enter.

  3. Get the files for perftune from http://java.sun.com/performance/JES/

  4. Backup, then replace the following: /opt/SUNWps/bin/pstune-env /opt/SUNWps/bin/pstune-portal with /opt/SUNWps/bin/perftune and /opt/SUNWam/bin/amtune

Secure Remote Access Administration Guide

The following items are not documented in the online help or Sun Java System Portal Server 6 2005Q4 Secure Remote Access Administration Guide, but are part of the Access Manager administration console.

ProcedureTo Enable Basic HTTP Authentication

Steps

  1. Log in to the Access Manager administration console as administrator.

  2. Select the Service Configuration tab.

  3. Click the arrow next to Gateway under SRA Configuration.

  4. The Gateway page is displayed.

  5. Select the gateway profile for which you want to set the attribute.

  6. The Edit Gateway Profile page is displayed.

  7. Click the Core tab.

  8. Select the Enable HTTP Basic Authentication checkbox to enable HTTP basic authentication.

  9. Click Save to record the change.

  10. Restart the Gateway from a terminal window:

    gateway-install-root/SUNWps/bin/gateway -n gateway-profile-name start

Online Help

The Search channel Help page states in the Advanced Search section:

Known Issues and Limitations

This section contains a list of the known issues with Portal Server 6 2005Q4. The following product areas are covered:

Installation


Gateway redirection not happening in any multi-session installation. (4971011)

Description:

Regardless of the installation mode, gateway redirection does not occur during a multi-session installation.

Solution:

Perform the following workaround:

  1. Launch a Portal Server browser and access the amconsole.

  2. Under “Service Configuration” tab, select “gateway.”

  3. In the lower right corner of the window, click the “default” and the “security” tab.

  4. Then, add a URL like http://IS-Host:port/amserver/UI/Login into “Non-authenticated URLs:” field.

    An example URL is http://boa.prc.sun.com:80/amserver/UI/Login.

  5. Finally, restart the Portal gateway by doing the following as superuser:

    /etc/init.d/gateway -n default start debug


The multiserverinstance script does not run on BEA WebLogic with Portal Server 6.3.1. (6228757)

Description:

If, during initial installation, the WebLogic admin port was specified as 7001 a different port number for the admin server can not be specified during the creation of a second instance.

Although the multi-instance script asks for the WebLogic admin port, and allows the user to provide a different value, changing the admin port or other admin server details is not supported.

By default it is assumed that all instances to be configured will be part of the same admin server.

Solution:

To point to a new admin server, perform the following steps:

  1. In the /etc/opt/SUNWps/PSConfig.properties file change the following properties to point to the new admin server:

    DEPLOY_ADMIN_PROTOCOL=

    DEPLOY_ADMIN_HOST=

    DEPLOY_ADMIN_PORT=

    DEPLOY_ADMIN=

  2. Use the multiserverinstance script to create the new instance.

Configurator


The Portal Server configurator does not work if Identity Server is running its Directory Server in LDAPS. (5044585)

Solution:

Disable the SSL for DS and update the AMConfig.properties with non SSL port to successfully install portal server.


Configurator not found in PortalServer-base/lib. (6209368)

Description:

After installing Portal Server packages, the Configurator is not found in the PortalServer-base/SUNWps/lib directory Configurator was a symbolic link to the psconfig script. Due to some packaging issues, the symbolic link was not created in Solaris (it is available in Linux). So the user can use the psconfig script directly.

Solution:

Use the psconfig script as an alternative.

PortalServer-base/SUNWPs/lib/configurator script is a symlink for the PortalServer-base/SUNWPs/lib/psconfig script.

Desktop


The Portal Desktop Notes channel does not use a semicolon as a separator. (4990900)

Description:

The Desktop online help states that a semicolon is used as a field separator. Semicolons are treated as regular text by the Notes channel, not as a field separator.

The pipe “|” symbol is now used as a filed separator.

Proxylet


iNotes and Microsoft Exchange 2000 SP3 are not supported with Proxylet. (no issue ID)

Description:

iNotes and Microsoft Exchange 2000 SP3 are not supported with Proxylet.

Solution:

None.


Page can not be displayed in iNotes when performing some functionalities. (6190570)

Description:

An error occurs with a message “Page cannot be displayed” in iNotes for the following modules:

  • Mail

  • Appointments

  • To Do

  • Contacts

  • Notebook

This message occurs when using the Save and Delete buttons.

Solution:

None.


NetFile help does not come up after Proxylet is downloaded. (6180420)

Description:

If Proxylet and NetFile are downloaded, the NetFile Help is not displayed and an exception is thrown in the Java console.

Solution:

None.


Unable to access the Portal Desktop in SSL mode after Proxylet is downloaded. (4990035)

Description:

The Portal Desktop can not be downloaded after Proxylet is downloaded if Portal Server is in SSL mode.

Solution:

None.


No help provided for the Proxylet rules. (5107957)

Description:

See Documentation Updates for Portal Server 6 2005Q4 for instructions on configuring Proxylet rules.


Accessing amconsole for a user from Proxylet gives “Action cancelled” page. (6190566)

Description:

If you log in to the Portal Desktop through the gateway, then load Proxylet, and then try to access the Administration console, the view list box will return an “Action Cancelled” page.

Solution:

None.


After an upgrade, the default Proxylet domain is not shown in the Proxylet edit rules window. (6230842)

Description:

After an upgrade, the default Proxylet domain is not shown in the Proxylet edit rules window.

Solution:

None.

Portlet


The portlet session is not stored across managed servers in a cluster. (6190600)

Description:

HTTP session failover for portlets doesn’t work.

Solution:

None.

WSRP


Can not create a new WSRP Consumer Producer. (6202285)

Description:

Creating a new WSRP consumer producer causes a server error.

Solution:

When using Application Server 8.1, remove the following four packages before performing the Java Enterprise System 3 installation process:

SUNWjaxp

SUNWxrgrt

SUNWxrpcrt

SUNWxsrt

Note –

If you have already installed Java Enterprise System 3 and experienced the errors described in CR 6202285, you should perform the following steps.

  1. Uninstall these four packages and reinstall them.

  2. Restart the system.

Online Help


The Online Help button for the Address Book channel is missing. (6193284)

Description:

The “Help” icon for AddressBook channel displays a “page not found” exception in the Browser.

Solution:

None.


The Portal Server Online Help links are broken in an Identity Server-Portal Server separated environment. (6197755)

Description:

This problem occurs when Portal Server is installed on the web containers, IBM WebSphere, and BEA WebLogic.

Solution:

For BEA WebLogic

  1. In a terminal window, on the Portal Server machine change to the following directory:

    cd /BEAInstall-base/user_projects/domains/mydomain/applications/DefaultWebApp

  2. Type:

    ln -s /AccessManager-base/public_html/online_help/ online_help

    If the DeafaultWebApp directory is not available in /BEAInstall-base/user_projects/domains/mydomain/applications, type the following commands in a terminal window:


    cp /BEAInstall-base/weblogic81/common/templates/applications/DefaultWebApp.jar /tmp 
cd /tmp jar -xvf DefaultWebApp.jar 
cd /tmp/_apps_/
cp -R DefaultWebApp /BEAInstall-base/user_projects/domains/mydomain/applications

For Websphere

  1. In a terminal window on the Portal Server machine, change to the following directory:

    cd IBMInstall-base/IBM/WebSphere/Express51/AppServer/installedApps/DefaultNode/DefaultApplication.ear/DefaultWebApplication.war

  2. Type:

    ln -s AccessManager-base/SUNWam/public_html/online_help/ online_help

Communication Channels


The Mail Channel does not display the login page. (4873659)

Description:

The Mail Channel will not successfully launch the Messenger Express client when the ipsecurity setting of the Sun Java System Messaging Server is set to “yes.” In order for the Mail Channel to successfully launch the Messenger Express client, the ipsecurity setting of the Messaging Server must be set to “no.”

Solution:

Set the ipsecurity setting of the Messaging Server to “no.”


The MailProvider will not work with SSL secured IMAP. (4919693)

Description:

The current MailProvider implementation will not work with SSL secured IMAP.

Solution:

After configuring the IMAPS channel, if the channel shows error on Portal Server with Web Server as container, change the mail.jar as the first entry in the CLASSPATH.

To add the mail.jar file as the first file in the classpath:

  1. Open the file ws-install-dir/SUNWwbsvr/https-ws-instance-name/config/server.xml

  2. Change the mail.jar file to be the first entry in the classpath.

  3. Restart the Web Server.


A newly created Address Book channel does not appear on the Desktop.(4922220)

Description:

The Address Book service must first be configured. Because the AddressBookProvider is not pre-configured, any channel the user creates based on the AddressBookProvider will not appear on the user’s Desktop or on the Content link unless the AddressBookProvider has been configured. See “Configuring the Address Book Channel” section in Chapter 17, and “SSO Adapter Templates and Configurations” in Appendix A of the Sun Java System Portal Server Administration Guide for more information.

Creating channels based on the other communications channels in the pre- populated, user-defined channels set may result in the created channel displaying the message: “Please specify a valid configuration.” Although the other Communication Channels are defined to a sufficient extent to appear on the user’s Desktop, they require additional administrative tasks in order to ascertain which back-end service to use.

Additionally, the communication channels require the desktop user to specify back-end credentials (such as user name and password) after the administrative tasks are completed. The desktop user can specify these values in the channel by using the channel’s Edit button.

Note –

The userDefinedChannels set might need to be administered on a per install basis because this set includes references to back-end services which might not apply to your particular setup. For example, all Lotus Providers in this set refer to interaction with Lotus back-end services for the communication channels which do not apply if none in the Portal user base will be using Lotus back-end services.


The Calendar channel will not launch if the domain name is not set. (4946959)

Description:

If the Server name in the Calendar channel does not include the fully qualified domain name, the Calendar channel does not launch.

Solution:

Verify that the fully qualified host name is used for the Server name setting.


The SSO Adapter Configuration Does Not Support Distributed and Redundant Personal Address Books. (5020452)

Description:

Prior version of the SSO Personal Address Book (PAB) Adapter expects the container o=pab to co-exist within the User and Group directory. Portal Server6 2005Q1 introduced support in the “SUN-ONE-ADDRESS-BOOK” adapter template to specify the PAB directory server. The following properties are now supported:

ugHost: LDAP host name for PAB lookup

ugPort: LDAP port for PAB lookup

Solution:

These properties need to be manually added to the “SUN-ONE-ADDRESS-BOOK” SSO adapter template by the admin in the Identity Server Administration Console.

  1. Log in to the Access Manager administration console.

  2. Select Service Configuration > SSO Adapater.

  3. Select “SUN-ONE-ADDRSS-BOOK” as the SSO Adapter template.

  4. Select Edit Properties > New Default.

    1. Specify “ugHost” for Name.

    2. Specify the LDAP host name.

    3. Select Create.

  5. Select Edit Properties > New Default.

    1. Specify “ugPort” for Name.

    2. Specify the LDAP port.

    3. Select Create.


The links in the Mail channel lead to the Portal Desktop instead of the Mail Client. (5053733)

Description:

When a user selects the Logout link from the Mail Channel, the logout page for the client logout page is not displayed (instead the Portal Desktop page is displayed).

Solution:

If this problem occurs, perform the following steps:

  1. Refresh the Portal Desktop.

  2. Click the Launch Mail link in the previous portal page, and the Mail client can launch again.

If you want a webmail login page after a logout (instead of the Portal desktop) do the following.

  1. Change the following code on the messaging server.

    The file /var/opt/SUNWmsgsr/config/html/main.js has a method restart(), which is called from exit(), which in turn is called from logout().


    function restart() {
var ref = window.document.referrer != ’’ ? window.document.referrer : ’/’
if (ref.indexOf(’mail.html’) > 0)
ref = ’/’
var ind = ref.indexOf(’?’)
self.location.replace(ind > 0 ? ref.substring(0, ind) : ref)
}

    Change the first line and provide the url of the mail server login page as follows:

    var ref = window.document.referrer != ’’ ? "http://pavoni:2080" : ’/’

  2. Restart the mail server.

  3. Clear the browser cache.

To test:

  1. Click Launch Mail.

  2. Log out from webmail.

  3. Click Launch Mail, which will take you to the webmail login page as the old session is not valid.


Clicking on the Launch Mail Link of UWC Mail Channel does not open MailBox. (6179802)

Description:

On clicking on the link of launch mail it takes to Web Server index page instead of the user’s inbox.

In Java Server Enterprise 3 the Portal Mail channel can launch the UWC from the Portal Desktop.

A new channel has been added called “UWCMail” and is based on the MailProvider. The UWCMail channel is available in the default organization or root suffix but is not associated with a Container out of the box. The UWCMail channel must be added to a container.

The UWCMail channel defines the following properties:

  • title

  • description

  • ssoAdapter

  • applicationHelperEdit

  • applicationHelperURL

The SSO adapter configuration is sunUWCMail and the SSO adapter template is SUN-UWC-MAIL.

Solution:

To use the new UWCMail channel, add the UWCMail channel to a container for the channel to be visible on the desktop.

  1. From the Access Manager Administration console, add the UWCMail channel to the My Front Page Tab.

  2. Edit the UWCMail channel and specify the server settings. For example, login to the Portal Desktop as a new user and edit the UWCMail channel by specifying the following values:

    • server name: messaging-server-name

      • imap server port: messaging-server-imap-port

      • user name: uid

      • user password: password

      • smtp server name: messaging-server-smtp-server-name

      • smtp server port: messaging-server-smtp-port

      • client port: messenger-express-client-port

      • mail domain: hosted-domain


The calendar does not come up on the UWC Calendar Channel. (6179806)

Description:

In Java Server Enterprise 3 the Portal Calendar channel can launch the UWC from the Portal Desktop.

A new channel has been added called UWCCalendar and is based on the CalendarProvider. The UWCCalendar channel is available in the default organization or root suffix but is not associated with a Container out of the box. The UWCCalendar channel must be added to a container.

The UWCCalendar channel defines the following properties:

  • title

  • description

  • ssoAdapter

  • ssoEditAttributes (exposes clientHost and clientPort)

  • applicationHelperEdit

  • applicationHelperURL

The SSO adapter configuration is “sunUWCCalendar” and the SSO adapter template is “SUN-UWC-CALENDAR.”

Solution:

To use this new channel:

Add the UWCCalendar channel to a container for the channel to be visible on the desktop.

  1. From the Access Manager Administration console, add the UWCCalendar channel to the My Front Page Tab.

  2. Edit the UWCCalendar channel and specify the server settings. For example, login to the Portal Desktop as a new user and edit the UWCCalendar channel by specifying the following values:

    • server name: calendar-server-name

      • server port: calendar-server-port

      • user name: uid

      • user password: password

      • client server name: uwc-client-server-name

      • client port: uwc-client-port


UWC Address Book is not being displayed on the UWC AddressBook channel. (6179807)

Description:

The SSO adapter implementation, WabpSSOAdapter, is using port instead of clientPort for the back end connection to the Address Book Server. This causes the Portal UWC Address Book to fail when the UWC client is not installed on port 80.

Solution:

You can workaround this problem by doing one of the following:

  • Install the UWC client on port 80

  • Set the SSO adapter template or configuration property port and the value to be the same as clientPort.

To set the SSO adapter template or configuration property port and the value to be the same as clientPort is to add the “port” as a “Merge” property specified at the Organization level. The Channel does not expose the “port” on the Channel’s edit page.

To add the port as a “Merge” property:

  1. Log in to the Access Manager Administration console.

  2. Select Service Configuration.

  3. Select SSO adapter.

  4. Select Edit Properties... for SUN-UWC-ADDRESS-BOOK.

  5. Select New Merge and specify:

    Name: port

  6. Select Create.

  7. Select Finished.

  8. Select Identity Management.

  9. Select the organization.

  10. Select Services.

  11. Select SSO adapter.

  12. Select Edit Properties... for sunUWCAddressBook and specify the properties.

  13. Select New Default and specify the port value and select Save.

    Note –

    If there are existing users with SSO adapter attributes written at the User level, this solution might not work since the existing users do not inherit the Organization level changes to the SSO adapter configuration. Instead, the SSO adapter template can be updated with the “host” and port defined as Default properties.


Microsoft Calendar and Microsoft AddressBook throw “Content not available” error. (6213120)

Description:

An error message stating that content is not available may be displayed when configuring the Microsoft Calendar and Address Book channels on a WebLogic server. This problem can occur when other files take precedence over the jintegra.jar file.

Solution:

Add the jintegra.jar file as the first file to the classpath.

To add the jintegra.jar file as the first file in the classpath:

  1. Open the file /usr/local/bea/user_projects/domains/mydomain/startWebLogic.sh.

  2. Edit the CLASSPATH to add /opt/SUNWps/web-src/WEB-INF/lib/jintegra.jar as the first jar file in the classpath.

  3. Restart the WebLogic server using startWebLogic.sh.


Lotus Address Book and Calendar does not work with old NCSO.jar. (6216069)

Description:

Lotus Address Book and Calendar need the latest version of NCSO.jar to work.

Solution:

Use the latest version of Domino, for example NCSO.jar from Domino 6.5.1.

Secure Remote Access


Calendar links not accessible via Portal Secure Remote Access. (4929710)

Description:

If the desktop user selects to display non-secure items, the Calendar desktop shows. However, none of the links appear. If the desktop user selects not to display non-secure items, the Calendar desktop does not show. The effect is that the Calendar desktop items can not work through the gateway.

Solution:

Edit /opt/SUNWics5/cal/config/ics.conf on the Calendar Server. Change the line, render.xslonclient.enable = “yes”


The Proxylet rules edit page gets displayed very late through the gateway. (6181714)

Description:

When invoking the Proxylet rules edit page through the gateway, the response is very slow, and Proxylet rules page takes a while to be displayed.

Solution:

None.

Gateway


After stopping and starting the Application Server, users can not log in through the Gateway. (6191449)

Description:

If the Portal Server is using the Sun Java System Application server as its web container, stopping and restarting the web container in some cases causes an error that prevents the user from being able to log in to the Portal Server through the gateway. The problem occurs for all webcontainers— Application Server S8.1, Web Server, BEA WebLogic and IBM WebSphere.

Solution:

Stop and restart the gateway. In a terminal window, type:

gateway-base/bin/gateway stop

gateway-base/bin/gateway start

NetFile


Files cannot be opened on the local host in the NetFile Java 2 applet. (5055476)

Description:

The Netscape 7.1 browser does not allow local files to be opened in the NetFile Java 2 applet.


A local file can not be opened in NetFile. (5033644)

Description:

A local file can not be opened in NetFile because the file’s base directory is removed. When a user expands a file directory tree and tries to find a local file such as /tmp/1.txt and the user clicks Open, the alert dialog pops up with the following error message: The file /1.txt can not be found. Please check the location and try again.

Solution:

None.


Adding a share in NetFile with the type “FTP,” causes an exception. (5053765)

Description:

Users can not add an ftp share in NetFile Java1 or Java2. This problem occurs on the Linux platform.

Solution:

Make sure that ifconfig is added to the system’s search PATH.


NetFile for NFS does not work on Linux 2.1. (6200718)

Description:

NetFile Java1 nor Java2 can access an NFS server shared mount on the Linux 2.1 platform.

Solution:

To use NetFile to access and NFS server shared mount, perform the following manual steps.

For BEA WebLogic:

Edit the startWeblogic.sh and startManagedWeblogic.sh scripts located in bea-install-dir/user_projects/domains/mydomain/ by adding the following line after the LD_LIBRARY_PATH variable:


LD_PRELOAD=/usr/lib/libpam.so:${LD_PRELOAD} ; export LD_PRELOAD

For Sun Java System Application Server:

Edit the asadmin script located at the AS8.1-install-dir/sun/appserver/bin by adding the following line after the LD_LIBRARY_PATH variable:


LD_PRELOAD=/usr/lib/libpam.so:${LD_PRELOAD} ; export LD_PRELOAD

For Web Server:

Add the following line under in the start script of the web container instance after the LD_LIBRARY_PATH variable:

ws-install-dir/sun/webserver/https-ws-instance-name/start 


LD_PRELOAD=/usr/lib/libpam.so:${LD_PRELOAD} ; export LD_PRELOAD

Netlet


Netlet fails to load after relogin. (2102626)

Description:

If Netlet is loaded, and you log out of the Desktop and then try to log back in, you will not be able to restart Netlet.

Solution:

Close the browser and open a new browser to load it again.


Microsoft Internet Explorer crashes while Loading Netlet with Default Microsoft JVM. (2120110)

Description:

When Netlet is loading, a security message is displayed. Clicking “yes” to continue causes Microsoft Internet Explorer to crash.

Solution:

None.

Rewriter


When using Microsoft Exchange 2003, gif files are missing in some of the pages. (6186547)

Description:

Many interface image files are missing.

Solution:

None.


In iNotes, under the Contacts tab, the Help page is redirected to the Administration console. (6186541)

Description:

Clicking the Help button from the Contacts tab in iNotes displays the Administration console page instead of the Help page.

Solution:

None.


iNotes does not logout correctly. (6186544)

Description:

Clicking on logout in iNotes displays two options. Neither of these options will log out of iNotes.

Solution:

None.


Microsoft Exchange 2000 SP3 gives warning messages and action cancelled messages. (6186535)

Description:

The following actions in Exchange 2000 SP3 it causes security warning messages and Action cancelled messages:

  • Clicking New tab under Mail.

  • Selecting any item in the drop box list.

  • Clicking New tab under Calendar.

  • Clicking on Empty Deleted Items folder.

  • Creating a new task.

Solution:

None


Microsoft Exchange 2003 returns a login page when clicking on the Calendar reminder page on the “open item” button. (6186528)

Solution:

None


When using Microsoft Exchange 2000 SP3, Moving or Copying messages to specific folders doesn’t work. (6186534)

Description:

If you login to the Portal Server through the gateway, and you edit the bookmark channel with the Microsoft Exchange machine details, the Move/Copy buttons on the Microsoft Exchange interface produce the error “Operation could not be performed.”

Solution:

None.


When using Microsoft Exchange 2000 SP3, selecting any item in the drop box list gives Action Cancelled message. (6186533)

Description:

If you log in to the Portal Server through the gateway, and you edit the bookmark channel with the Microsoft Exchange machine details, the mail and calendar drop box list on the Microsoft Exchange interface do not work. An “Action cancelled” message is displayed.

Solution:

None.


When using Microsoft Exchange 2000 SP3, Clicking on empty deleted items folder displays Action Cancelled. (6186540)

Description:

If you log in to the Portal Server through the gateway, and you edit the bookmark channel with the Microsoft Exchange machine details, deleted items can not be emptied in the Microsoft Exchange interface.

Solution:

None.

Documentation


The Sun Java System Portal Server 6 2004Q2 Administration Guide provides the wrong pathname for starting the Application Server. (5069886)

Description:

Chapter 2 of the Sun Java System Portal Server 6 2004Q2 Administration Guide uses the wrong pathname for the Sun Java System Application Server start command. The path /var/opt/SUNWAppserver7/domains/domain1/admin-server/bin is incorrect.

Solution:

The correct path is /var/opt/SUNWappserver/domains/domain1/bin.


The gateway does not do round robin on portal server list as mentioned in the documentation. (6286205)

Description:

The Portal Server documentation states that the gateway uses the Portal Server list in a round-robin fashion. In the Java System Enterprise 3 release, the gateway goes through the Access Manager list in a round-robin fashion rather than using the Portal Server list.


Missing line in the instructions for running the configurator in a localized environment for Solaris Sparc or X86 machines. (6238677)

Description:

Chapter 2 of the Sun Java System Portal Server 6 2005Q1 Administration Guide contains an error in the command for running the configurator in a localized environment for Solaris Sparc or X86 machines.

The correction is as follows:

To run the configurator in a localized environment on a Solaris Sparc or x86 machine, type the following as one line:

/usr/jdk/entsys-j2se/bin/java -DPS_CONFIG_DEBUG=y
-DDEPLOY_ADMIN_PASSWORD=<deploy admin password>
-DDS_DIRMGR_PASSWORD=<LDAP directory manager password>
-DIDSAME_LDAPUSER_PASSWORD=<AM ldap user password>
-DIDSAME_ADMIN_PASSWORD=<AM admin password>
-DBASEDIR=PS-INSTALL-DIR
-cp PS-INSTALL-DIR/SUNWps/lib/configL10N.jar
com.sun.portal.config.ConfigureL10N

For Secure Remote Access, the command for running the L10N configurator is:

/usr/jdk/entsys-j2se/bin/java -DPS_CONFIG_DEBUG=y
-DDEPLOY_ADMIN_PASSWORD=<deploy admin password>
-DDS_DIRMGR_PASSWORD=<LDAP directory manager password>
-DIDSAME_LDAPUSER_PASSWORD=<AM ldap user password>
-DIDSAME_ADMIN_PASSWORD=<AM admin password>
-DBASEDIR=PS-INSTALL-DIR
-cp PS-INSTALL-DIR/SUNWps/lib/configL10N.jar
com.sun.portal.config.ConfigureL10N

Chapter 6 of the Sun Java System Portal Server 6 2005Q1 Administration Guide contains an error in the commands for starting the Application Server web container. (5070356)

Description:

The directory location for the start command is incorrect.

Solution:

The command for starting the Sun Java System Application Server should be:

  1. Change directories to the location of the start command.

    • For Solaris use the command cd /opt/SUNWappserver7/sbin

    • For Linux use the command cd /opt/sun/appserver/bin

  2. Type the following command: ./asadmin asadmin> start-domain --user admin domain1 asadmin> exit


Chapter 18 of the Sun Java System Portal Server 6 2005Q1 Administration Guide contains the wrong path for the desktopconfig.properties file. (no issue ID)

Description:

The section “Debugging Portal Server” in chapter 18 of the Sun Java System Portal Server 6 2005Q1 Adminstration Guide states that the desktopconfig.properties file is located in /etc/opt/SUNWps.

The correct file location is /etc/opt/SUNWps/desktop.


Misleading documentation about sendrdm Command Line Interface tool. (5078733)

Description:

Chapter 16 of the Technical reference guide states the following:

The sendrdm command provides a mechanism for a CGI or command-line based search. An RDM (resource description manager) request is sent in SOIF format to the Search server. This command is normally run in a search-enabled Sun Java System Portal Server instance directory, which is the /server-instance-directory/deployment_uri directory. This is the deployment URI path you selected at install time. If you chose the default Portal Server install, this is the /var/opt/SUNWps/https-servername/portal directory. Where the value of the servername is the default web Portal Server instance name--the fully qualified name of your Portal Server.

This should state that

If you chose the default Portal Server install, this is the /var/opt/SUNWps/https-instance-name/portal directory. Where the value of the servername is the default web container instance name--the fully qualified name of the machine, for example sesta.sun.com.

Mobile Access


The native JSP desktop does not handle the case when the frontPageSize exceeds the maximum deck size (Wm1DeckSize). Please refer to http://docs.sun.com/source/817-5323/index.html. (4950078)

Solution:

None.


Mail is sometimes displayed as HTML document. (4938743)

Description:

Email messages sent with HTML in the body are displayed with the HTML source.

Solution:

No workaround is available. However, to preserve the original formatting of messages, change the settings for mail application to plain text.

To do this in Netscape, use the mail client to complete the following tasks:

  1. From the Edit option on the menu > Preferences > Mail & Newsgroups

  2. From the Mail & Newsgroups menu, click Send Format and it will display the Send Format Preferences.

  3. Select Convert the Message to Plain Text option and click OK.

For the Outlook Express client:

  1. Select tools -> Options -> Send.

  2. In the “Mail Sending Format” section, pick “Plain text” instead of “HTML.”

  3. Select Save.


The default value shown in the Document Root Directory of the Portal Server Configuration Panel during JES installer is incorrect. (6203728)

Description:

This issue arises when Portal Server is installed independently after other dependent products have been installed and configured and while installing Portal Server on a separate instance other than that of Access Manager.

Solution:

If the Web container on which the Portal Server is deployed is Sun Java Enterprise System Web Server, make sure that the correct path for Document Root Directory is entered in the Portal Server Configuration Panel that appears while running the JES installer.

For example, if you have installed the Sun Java Enterprise System Web Server in */opt/SUNWwbsvr*, then the Document Root Directory would be */opt/SUNWwbsvr/docs*.


The Contents link in the Mobile Application Services page displays “bad request” message. (5043783)

Description:

A bad request error occurs only when you click the Contents link in the Help page for the Services option. This happens while accessing Help from the Administration Console for Access Manager > Identity Management tab.

Solution:

None.


The Views: Rule for Date Contains does not work. (6212818)

Description:

Date search using a string format as dd/mm/yyyy in the search filter will not work.

Solution:

IMAP stores dates in this format: Wed, 04 Jun 2003 13:06:55 -700. Search filters using this format should work.


When a View name contains a space, the View link does not display. (6212854)

Description:

The View link does not display on a device if the View name begins or ends with a space. Clicking Edit View results in a null pointer exception.

Solution:

Do not use leading or trailing spaces in view and rule names.


URL forwarding to minimize URL length for mobile and desktop users. (5020380)

Description:

URL forwarding will be required to minimize URL length for desktop and phone users.

Solution:

You can use redirection to seamlessly send users requesting a document on one server to a document on another server. For example, if the user types http://home.suncom.net, it is without a destination URI. This prefix is not interpreted and translated in the web server administration console as the following:

Prefix: /index.html

To fix URL:

http://home.suncom.net/amserver/UI/Login?module=MSISDN

The web server will forward all Portal URLs with an URI /index.html to the fixed URL. Check the web server instance obj.conf file for this entry:

NameTrans fn="redirect" from="/index.html"
url-prefix="http://portal.mobile.suncom.net/amserver/UI/Login?module=MSISDN"

Mobile Mail & AddressBook Preferences are not documented. (5011510)

Solution:

None.


Using Application Server 7.1 UR1 in the cookieless mode. (5107310)

Solution:

When using Application Server 7.1 Update Release 1 (UR1), if users need to use the cookieless mode, add the following JVM option to the Application Server configuration:

-DJ2EEDecodeURI


Invalid Rule/View URL Syntax error when rule is applied properly on a browser using Japanese language. (6190033)

Description:

When users add a rule on a browser using Japanese language, “Invalid Rule/View URL Syntax” error message is displayed. This error does not occur on browsers using English language.

Solution:

None.


Web server always sets content type to text/html when servlet filter is set. (6174754)

Description:

When a user deploys the Portal Gateway with an Access Manager instance, which is deployed on Sun Java System Web server, the Web Server always sets the content type to text/html. The following workaround provided will help users to work through the Web Server bug 6173293, which causes gateway bug 5093084.

Solution:

Make the following change to the obj.conf file in the web-server-instance/config directory.

  1. Change the ObjectType from:


    ObjectType fn=force-type type=text/html

    to:


    # ObjectType fn=force-type type=text/html

  2. Restart the web server after you have made this change.


Changing client type in palmOne Treo 180 device to cHTML. (6190070)

Description:

When a palmOne Treo 180 mobile device accesses Mobile Access, the contents are rendered using the WML markup language. The Treo 180 is a cHTML capable mobile device. Though the Treo180 devices are capable of displaying WML, cHTML is preferable because cHTML is a richer markup language.

Solution:

The following steps will enable you to change the client type to cHTML using amconsole:

  1. Navigate your browser to http://hostname:port/amconsole.

  2. Login as an administrator.

  3. Click on Service Configuration tab -> Client Detection -> Client Types: Edit (on the right panel).

    The Client Manager is displayed.

  4. Select the WML category to get the list of WML capable devices.

  5. Edit UPG1_UP_4.0_(compatible__Blazer_1.0) and change the “Immediate parent type for this device” to cHTML.

  6. Save the device settings, and then save global Client Detection settings.

    For more information about changing Client types, see Using the Client Manager in Chapter 2, Managing Mobile Devices of the Sun Java System Portal Server, Mobile Access 6.2 Administrator’s Guide.


Anonymous Portal login from a mobile throws a serious desktop error. (6184377)

Description:

When users access Portal Server using anonymous login from a mobile using XHTML or WML Browser or WML / XHTML Simulators the following error message is displayed.

“A serious error has occurred in the Desktop. This may have been caused by a mis-configuration on the server. Please report this problem to your administrator.”

Solution:

None.


Views menu option from mail is not displayed on Mobile desktop. (6185041)

Description:

When using a CC/PP enabled phone, the correct device name may not be displayed in the “Mobile Devices” section of the Portal Desktop. Users will be unable to associate views with the device. It may not be possible for users to customize content or layout for the device. Using amconsole, the following workaround will enable the Views menu option on your mobile device.

Solution:

Users must add the device name manually to the user’s profile. The correct device name for a CC/PP compliant device is the URL of the CC/PP profile with special characters replaced with “_” and with a “_” character at the beginning and the end. For example, if the URL is http://developer.openwave.com/uaprof/OPWVSDK62.xml, then the device name is _http___developer.openwave.com_uaprof_OPWVSDK62.xml_. The following steps describes how you can add the device name to the user’s profile.

  1. Navigate your browser to http://hostname:port/amconsole.

  2. Login as an administrator.

  3. Click on Users -> click a user -> Services -> Portal Desktop -> Edit -> Edit XML directly.

  4. Locate the <Collection name="selectedClients"> tag.

    This tag lists all the selected client devices.

  5. Add the following tag:

    <String name="_http___developer.openwave.com_uaprof_OPWVSDK62.xml_" value=""/>

  6. Save your changes.

  7. Login to the Portal Desktop as an User.

  8. New mobile device called

    _http___developer.openwave.com_uaprof_OPWVSDK62.xml_ displays.

  9. Attach a new mail view to this device.

  10. Login using the Openwave 6.2 (xhtml) simulator.

  11. The Views menu displays.

    Note –

    The string added to the selectedClients collection is the URL of the CC/PP profile, with special characters replaced with “_”. You need to repeat the above steps for each CC/PP device you plan to support. The URL can be found either in the HTTP headers, or in the CCCPPClientDetector log file (in /var/opt/SUNWam/debug).


No Online Help available for Mobile Mail Preferences. (6185112)

Description:

When users access Mobile Mail Preferences link by clicking Edit Mail from the Portal Desktop, no help is displayed for Mobile Mail Preferences.

Solution:

None.


Devices rendering HDML content display garbage for Japanese characters for detail pages for Calendar, Mail, and Address Book. (6191363)

Description:

When users view their Calendar, Mail, and Address Book the content gets corrupted for Japanese locale when viewing HDML content. For example, when users:

  • Login to mobile desktop, the contents are displayed and Japanese characters are also displayed.

  • Navigate to the Calendar, the Calendar page contents are displayed and Japanese characters are also displayed

  • View Calendar, the Japanese characters in the Calendar events get corrupted.

Same problem happens for Mail and Address Book. Mobile desktop (top page) and the primary page of the Calendar, Mail, and Address Book are OK but when users are browsing the contents, the pages become garbage. For other types of content this issue does not appear.

Solution:

None.


Mail and calendar events sent in Japanese from browser, and then viewed on handset are corrupted and vice versa. (6191389)

Description:

While adding a Japanese calendar event from a mobile device, the event is displayed on a device but when displayed on a browser the Japanese characters gets corrupted. Also, when users add a Japanese event from a browser the event displays on a browser but gets corrupted when displayed on a mobile device. Similarly, when users use a browser to send a mail in Japanese, and view the mail on a mobile device the characters are corrupted. When users send a mail from the mobile device the email is displayed on a device but gets corrupted when displayed on a browser.

Solution:

None.


Portal Server Mobile Access Upgrade Files are Updated (no issue ID)

Description:

The Portal Server Mobile Access files used when upgrading from Sun ONE Portal Server 6.2 to Sun Java System Portal Server 6 2005Q1 for Solaris SPARC (java_es_05Q1_portal_mobile_access_sparc_solaris8.tar.gz) and for Solaris x86 (java_es_05Q1_portal_mobile_access_i386_solaris9.tar.gz) have been updated and are available for download from:

http://wwws.sun.com/software/download/products/41391049.html

Localization


Self-registered users can not launched localized file. (4934330)

Description:

NetFile launchs in English, even if the user sets the locale to a non en_US value.

Solution:

After self registration, , and and button.

  1. Go to “Edit User Information.”

  2. Confirm the user language.

  3. click OK.


The date and time are not displayed according to the locale in the Calendar. (4971337)

Description:

On the Portal Desktop, the date and time are not displayed in the correct locale format. For example, if the Korean locale package is installed, the date and time format in the Calendar are not displayed in Korean. This issue will occur for any localized installation of Mobile Access Pack.

Solution:

None.


Reminder time for Calendar task does not accept modification. (5031431)

Description:

Add a task to the Calender and set the reminder time as 15 minutes. When modified, that task’s reminder time is shown as 1 minute though it shows as 15 minutes in Calendar Express.

Solution:

None.


The Date in NetFile depends on locale of the server. (5026281)

Description:

The date format should depend on the user’s locale not the server’s locale.

Solution:

None.


Chinese text file attachment can not be saved correctly in Netmail. (5031446)

Description:

When using Netmail to attach a text file that contains Chinese characters, users who receive that file by Netmail, can not save the file correctly. The file characters are corrupted.

Solution:

None.


Unzipping a multibyte file in which the filename is a multibyte filename causes the filename to get corrupted. (5033641)

Description:

If a multibyte file that has a multibyte filename is unzipped the filename gets corrupted.

Solution:

None.


The naming order of address book entries is strange for Japanese users. (6197714)

Description:

The address book channel and map address book displays first name then last name. It should display last name, then first name.

Solution:

None.


When using Netmail Lite to send mail in Japanese, the end of the message displays either question marks or garbage characters.(6197737)

Solution:

None.


When using the de_DE locale, the advanced search page is incorrect. (6208359)

Description:

After clicking the search tab, the advanced search page comes up but part of the page is missing.

Solution:

None.


The Proxylet (under Secure Remote Access) configuration page in the Administration Console is not localized. (6208800)

Solution:

None.


The edit page of the Instant Messaging Channel displays an error page. (6210507)

Description:

Clicking the edit button of the Instant Messaging channel causes an error page to be displayed.

Solution:

Change to user locale to English and then edit the Instant Messaging channel.


Multibyte filenames in NetFile can not be displayed under an NFS server’s shared folder. (6193843)

Description:

Non-English users can not access NetFile files through the Portal Server desktop under NFS server’s shared folder if the file has a multibyte character file name.

Solution:

None.


Clicking on the “Edit” button of a channel with a multibyte name causes an empty page to be displayed. (6193860)

Solution:

None.


Can not post a note in the Notes channel. (6193889)

Description:

Portal desktop users are unable to post a note in Notes Channel because the channel can not be edited.

Solution:

Change the display profile fragment for NoteProvider in dp-providers.xml file as shown (in bold) below:

<Provider name=”NotesProvider” class=”com.sun.portal.providers.notes.NotesProvider”>

<Boolean name=”isEditable” value=”true” advanced=”true"/>


The time format in the Calendar channel is incorrect for Japanese users. (6196579)

Description:

For Japanese users, the time format on calendar channel should be PM: HH:MM - AM: HH:MM.

Solution:

None.


Users can not cancel the Netlet warning dialog box. (2112878)

Description:

When Portal Server desktop users try to access an FTP or telnet service through Netlet in a localized Portal Server configuration, Netlet displays a warning dialog box with the options “OK” and “Cancel.” If the user clicks Cancel, the dialog box hangs.

Solution:

None.


Instant Messenger can not be invoked as Java Web start style in with some JDK versions. (6199908)

Description:

This problem occurs when the user tries to access the Portal Server desktop on a Windows machine with J2SE 1.5.0 installed.

Solution:

None.


Unable to send mail using NetFile Java1. (4910252)

Description:

Files can not be sent using the mail button from NetFile Java1, when file path or file name contains multi-byte characters.

Files can not be mailed using the mail button from NetFile Java1. Files can be mailed using NetFile Java2.

Solution:

None.


The date format specified in the Netmail Online Help is wrong. (4920181)

Description:

The Netmail Online Help states that the date format to search for mail is mm-dd-yy. This format is incorrect in many locales.

Solution:

The date format for searching mail depends on the user’s locale. For example, in the Japanese locale, users should use the following date format:

yyyy/mm/dd


The date format used in the Calendar channel for some European (EMEA) locales is wrong. (5033728)

Description:

The date format used is Month Day, Year. The format should be Day Month Year.

Solution:

None.


Events in the Calendar channel use the wrong time format for European locales. (5033735)

Description:

Events displayed in the Calendar channel use the wrong time format (12-hours). They should use the 24-hour format as it is set in Calendar Server.

Solution:

None.


The Korean version of Netmail’s Find application does not locate all messages properly. (5036419)

Description:

The before/on option does not highlight messages that match the on value. The after/on option highlights messages that match the on value.

Solution:

None.


For simplified Chinese users, the default language in the User Information channel’s editing page is English. (5036625)

Description:

The locale XML files are set for en, not zh.

Solution:

None.


The Anonymous desktop (/portal/dt) is not displayed according to the preferred language set in the browser. (5059646)

Description:

The first time the anonymous desktop is accessed it is displayed according to the preferred language specified in the browser. If the preferred language is changed in the browser and the page is refreshed, only part of the desktop contents are displayed in browser locale.

Solution:

None.


When languages are selected, configuration of localization is slow. (5074720)

Description:

Portal Server software configuration requires several minutes for each language. Each language uses many XML files, and dpadmin is called for each.

Solution:

None.


Localized authentication JSPs for Portal Server Mobile Access are not deployed into the Access Manager. (6191601)

Description:

These JSPs are delivered in the SUNWam/mobile_auth_jsps.jar and must be unjarred into SUNWam/web-src/services. The SUNWam/amserver.war also must be recreated and redeployed into the web container.

Solution:

None.


Portal Server May Not Deploy for Spanish Locale. (6214289)

Description:

Portal Server may not start when deployed with Sun Java System Web Server if Portal Server was installed using the text-based interface.

Solution:

None.


NetFile Does Not Correctly Display Windows 2000 Shared Folder Names for Japanese Locale. (6215099)

Description:

The folder name is displayed as garbage only for the Japanese locale.

Solution:

None.

Known Issues and Limitations for the Sun Java Enterprise System 4 Release

Installation


The Application Server log contains Java exceptions, but the install is successful. (6320674)

Description:

The following Exceptions may appear in the Application Server log during the Portal Server installation:

java.lang.ClassNotFoundException:

com.sun.mobile.filter.AMLController

Solution:

None. This behavior is normal.

Access Manager


Installation of Access Manager on BEA WebLogic 8.1 throws an exception. (6285776)

Description:

Installing Access Manager on the BEA WebLogic 8.1 web container causes an exception to be thrown in the BEA WebLogic logs.

Additionally, errors occur when starting WebLogic and when logging into amconsole.

Solution:

None.

Communication Channels


The password field for the communication channels displays the password. (6280707)

Description:

The password filed for the communication channels contains the value before the channel is configured.

Solution:

None.


The Universal Web Client (UWC) Calendar does not come up through the gateway. (6218353)

Description:

Clicking the Launch Calendar link displays an error message.

Solution:

Perform the following steps in the gateway for UWC to work with the gateway.

  1. Login to Admin Console and click on the gateway profile under Service Management.

  2. Enable cookie management under the core tab.

  3. Add Calender, Messaging and UWC urls with port numbers in the list box for “URls to which session forwarded.”

  4. Under the Rewriter tab, enable Rewrite all URLs.

  5. Restart the gateway.


The Launch Address Book link does not appear if proxy authentication is enabled. (2126154)

Description:

By default, when UWC is enabled, the cookie webmailsid is used by Messenger Express. The Launch Address Book does not appear for the Portal AddressBook channel. The appropriate options must be set in order to workaround this bug.

Solution:

Use one of the following workarounds:

  • If UWC is installed, the option local.webmail.sso.uwcenabled is set to “1” for Messaging Server. This value signals Messenger Express to use a cookie. Set the option local.webmail.sso.uwcenabled to “0” with the configutil tool.

  • Verify that the option local.service.http.cookiename is left blank or is not set.

Secure Remote Access


The installer doesn't check to verify if the required rpm is installed. (6295727)

Description:

The installer doesn't check Linux systems to verify if the required rpm (gettext-0.10.38-7.rpm) is installed.

Solution:

None.

Gateway


The amconsole Login Page after a fresh install is different from the amconsole Login Page after an upgrade of Access Manager. (6295051)

Description:

The amconsole Login Page that is displayed after a fresh install is different from the amconsole Login Page after an upgrade of Access Manager from Java Enterprise System 3 to Java Enterprise System 4.

The Logout page that is displayed is also different between a fresh install and an Access Manager upgrade.

Solution:

Restart the Mozilla browser to get the correct login or logout page.


The Secure Remote Access init scripts try to run /etc/init.d/cron. (6300415)

Description:

The init scripts for the Secure Remote Access proxies (netletd and rwproxyd) try to stop and start cron using /etc/init.d/cron, but cron is managed by SMF in Solaris 10.

Solution:

On a Solaris 10 system, after starting the gateway watchdog process, issue the command:

svcadm restart cron

WSRP


WSRP functionality is broken on Linux with the BEA WebLogic 8.1 web container. (6285752)

Description:

During configuration of the WSRP producer, adding the created producer and consumer causes an error to occur.

Solution:

None.

Search


Need instructions for removing components except search server. (6298021)

Description:

No easy way exists to remove all components except a search server during the unconfiguration process.

Solution:

Use the following example to specify a search server that does not exist.

<?xml version = "1.0" encoding = "UTF-8"?>
<PortalServerConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="file:///opt/sun/portal/lib/psconfig.xsd">
        <Unconfigure ConfigurationHostName="HOSTNAME.DOMAIN" Validate="true" UnconfigureAll="false">
                <AccessManager>
                        <UserCredentials
                                AdministratorUID="amadmin"
                                AdministratorUserPassword="AMADMIN.PASSWORD"
                                LDAPUserId="amldapuser"
                                LDAPUserIdPassword="AMLDAPUSER.PASSWORD"
                                DirectoryManagerDn="cn=Directory Manager"
                                DirectoryManagerPassword="DIRECTORY.MANAGER.PASSWORD"/>
                </AccessManager>
                <PortalConfiguration>
                        <ComponentsToConfigure>
                                <component>portalserver</component>
                                <component>sracore</component>
                                <component>gateway</component>
                                <component>netletproxy</component>
                                <component>rewriterproxy</component>
                        </ComponentsToConfigure>
                        <SearchServer SearchServerID="nonexistentSearchServer"></SearchServer>
                        <PortalServer PortalID="MyFirstPortal">
                                <Instance InstanceID="nicp204_80"></Instance>
                        </PortalServer>
                        <PortalServer PortalID="MySecondPortal">
                        </PortalServer>
                        <Gateway Profile="default"/>
                        <NetletProxy Profile="default"/>
                        <RewriterProxy Profile="default"/>
                </PortalConfiguration>
        </Unconfigure>
*/PortalServerConfiguration>

Redistributable Files

Sun Java System Portal Server 6 2005Q4 does not contain any files which you can redistribute.

How to Report Problems and Provide Feedback

If you have problems with Sun Java System Portal Server, contact Sun customer support using one of the following mechanisms:

So that we can best assist you in resolving problems, please have the following information available when you contact support:

If you have problems with Sun Java System Portal Server, Mobile Access, please have the following information available when you contact support:

If your problems seem to be associated with a client, please have the following information available:

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Use the web-based form to provide feedback to Sun:

http://www.sun.com/hwdocs/feedback

Please provide the full document title and part number in the appropriate fields. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the part number of these Release Notes document is 819-2575.

Additional Sun Resources

Useful Sun Java System information can be found at the following Internet locations: