|
Sun Java System Portal Server 6 2005Q1 Release Notes |
Sun Java™ System Portal Server Release Notes
Version 6 2005Q1
Part Number 817-7699
These Release Notes contain important information available at the time of release of Sun Java System Portal Server 6 2005Q1. New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Portal Server 6 2005Q1.
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.
Release Notes Revision History
About Portal Server 6 2005Q1The 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 section includes:
What’s New in This Release
The following Secure Remote Access features are new and have not been documented in the Sun Java System Portal Server Secure Remote Access 6 2005Q1 Administration Guide.
- HTTPS Support in Proxylet. This implementation has the following results:
- Decryption is done at the client server.
- You can access destination servers running in SSL mode.
- Can directly present client certificate to the destination server.
- Basic authentication single sign on is no longer available at the gateway. (The Gateway can not insert SSO information in http headers.)
- URL-based access control is no longer supported, only host-based access control,
- External accelerators and external reverse proxies in front of the GW are not currently supported.
- This support is not for Proxylet with Portal Server on HTTPS.
- The Proxylet Java applet now has rules that determine the content of the PAC file. All HTTP requests go to Proxylet. The Proxylet rules allow the administrator to specify mappings based on protocol, host, or port to domains.
- Using the Access Manager administration console, the Portal Server administrator can choose whether to launch Netlet with Java Web Start or the Netlet applet. If the administrator chooses Java Web Start, when the user clicks Netlet icon on the desktop, the browser is launched and Netlet runs. When using Java Web Start, once it is deployed, Netlet does not need to be downloaded again.
Portal Server Patch Information
A required patch has been released for the Portal Server 6 2005Q1 product. This patch contains some upgrade related fixes and other miscellaneous fixes. Patch IDs for this consolidation are:
The patch Readme file contains a list of bugs that are fixed by the patch and the installation instructions. To download the patch and view the patch readme, go to http://sunsolve.sun.com and enter the patch id in the patchfinder field.
The order in which the patch is applied depends on whether your Portal Server installation will be a new installation or an upgrade.
Installing the Patch on a New Installation of Portal Server
To install the Portal Server patch on a new installation of Portal Server, run the JES installer and install the Portal Server product first.
Installing the Patch for a Portal Server Upgrade
If you are performing an upgrade from Portal Server 6 2004Q2 to Portal Server 6 2005Q1, the Portal Server 2005Q1 required patch must be installed as an interim step in the upgrade process. Perform the upgrade in the following order.
Bug Fixes in the Required Patch
The following table lists the bugs that are fixed by the Portal Server 6 2005Q1 required patch.
Hardware and Software Requirements for Solaris
The following hardware and software are required for this release of Portal Server.
Hardware and Software Requirements for Linux
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.
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.
To run psconfig:
- As root in a terminal window, go to the directory that contains the psconfig script:
cd PortalServer-base/lib
- Configuration can be performed in either the interactive mode or using a silent file.
./psconfig -s pssamplesilentfile
See Configuring Portal Server in Silent Mode.
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.
The Checklists are organized in the following way:
Portal Server And Secure Remote Access Configuration Checklist
is a three column table that lists 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.
Table 6 Portal Server Configuration Checklist
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.
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.
Deployment Information
PS_DEPLOY_TYPE
The web container on which Portal Server is being deployed. The Portal Server can be deployed on
Sun Java System Application Server 7.0
Sun Java System Application Server 8.1
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.
Web Container Information
Sun Java System Web Server
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.
Web Container Information
Sun Java System Application Server 7.0
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.
Web Container Information
Sun Java System Application Server 8.1
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.
Web Container Information
BEA WebLogic Server Checklist
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.
Web Container Information
IBM WebSphere Application Server
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.
Portal Server Information
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.
Identity Server Information
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.
Secure Remote Access Information (for configuring Secure Remote Access Support)
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 2005Q1 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
is a three column table for the Gateway Installation 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.
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.
Configuring Portal Server in Interactive Mode
Portal Server
is a three column table that lists 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.
Table 10 Portal Server Configuration Checklist
Question
Default Value
Description
COMPONENTS
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
To Configure multiple components, Use comma (,) to separate entries.
CONFIGURATION_MODE
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.
Portal Server Configuration Information
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
2. Sun Java System Application Server 8.1
3. Sun Java System Application Server 7.0
4. BEA WebLogic Application Server
5. IBM Websphere Application Server
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 8.1
3 = Sun Java System Application Server 7.0
4 = BEA WebLogic Server 8.1 SP2
Web Container Information
Sun Java System Web Server
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.
Web Container Information
Sun Java System Application Server 7.0
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.
Web Container Information
Sun Java System Application Server 8.1
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.
Web Container Information
BEA WebLogic Server
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.
Web Container Information IBM
WebSphere Application Server
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.
Portal Server Information
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
Identity Server Information
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.
Secure Remote Access Core Configuration Information (for configuring Secure Remote Access Support)
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
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.
Netlet Proxy
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.
Rewriter Proxy
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.
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-base/lib and execute the psconfig script.
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:
Portal Server
To access the Portal Server or the Identity Server administration console the directory server and the web container must first be started.
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
To start the Sun Java System Web Server:
or
Sun Java System Application Server 7.0
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.
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.
Sun Java System Application Server 8.1
To configure the Application Server Instance, do the following:
- 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
- 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
BEA WebLogic Server
When deploying the Portal Server on BEA WebLogic Server, perform the following steps following the installation of the Portal Server software.
- Check the /var/sadm/install/logs/Java_Enterprise_System_install.BMMddhhmm file for errors.
MM = month
dd = day
hh = hour
mm = minute
- Stop all BEA WebLogic Server instances (the admin and managed servers).
- Start the BEA WebLogic admin server instance. If you have installed on a managed instance, start the managed instance too.)
- 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.
- 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.
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.
IBM WebSphere Application Server
- Check the /var/sadm/install/logs/Java_Enterprise_System_install.B/MMddhhmm file for errors.
- 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.
- 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.
To Install JSR168 Sample Portlets and WSRP Samples On BEA WebLogic or IBM WebSphere
The following procedure applies only to Portal Server installations on the Solaris platform.
- Restart the BEA WebLogic 8.1 or IBM WebSphere Application Server 5.1 instance.
- Execute the following commands to install JSR168 Portlet samples.
PortalServer-base/lib/postinstall_PortletSamples
Provide the Access Manager admin password and application server admin password when prompted.
The portletsamples.war file is deployed.
- Make sure that the PATH setting includes /usr/bin. This is needed for awk part of script to run correctly.
- Execute the following commands to configure WSRP samples.
To Install WSRP Samples On Web Server or Application Server
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:
Secure Remote Access
When using the Portal Server with the gateway, the gateway Certificate Authority (CA) certificate must be added to the Portal Server trusted CA list, regardless of whether the Portal Server is running in HTTP or HTTPs mode.
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.
To create HttpsURLConnection, the Java Virtual Machine (JVM™) property -Djava.protocol.handler.pkgs needs to be set.
If Portal Server is running on the Sun Java System Web Server, Sun Java System Application Server, or BEA WebLogic Server, this property is correctly set to com.iplanet.services.com by default. The Sun Java System Identity Server package has the implementation of HttpsURLConnection and it provides an option to accept self-signed certificates from any SSL server by adding the flag com.iplanet.am.jssproxy.trustAllServerCerts=true in the AMConfig.properties file.
The -Djava.protocol.handler.pkgs is not set by default for the IBM WebSphere Application Server. The HttpsURLConnection implementation for supported application servers must use their own default handler (this could be JSSE or custom SSL implementation).
Configuring Multiple Gateways on Multiple Portals
When installing a second gateway on a second portal, you must manually update the Forward Cookie URLs value to point to the second Portal.
Starting and Stopping the Gateway
- 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:
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.
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.
Verifying the Portal Server Installation
Access the Portal Server Administration Console and Desktop
To Access the Sun Java System Identity Server Administration Console
- Open a browser.
- Type protocol://hostname.domain:port/amconsole
For example,
http://example.com:80/amconsole
- 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.
Verifying the Gateway Installation
- 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.
- 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.
- 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 InformationThis section contains the latest information that is not contained in the core product documentation. This section covers the following topics:
Installation Notes
Portal Server
For Java Enterprise System 6 2005Q1, Portal Server can be installed and configured to run with either:
To Run the Liberty Samples
The liberty samples are designed for a Portal Server and Access Manager installation on the same system.
To run the Liberty samples on a Portal Server/Access Manager separated install, do the following:
- Make sure the SP_HOST_DOMAIN value in configSP.sh points to the Access Manager full install host.
- 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:
- Change “Single Sign-On Failure Redirect URL” and set it to http://portal-server-host:port/portal/dt?libertySSOFailed=true
To set this value:
- 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:
- Go to Identity Management, Select Users from the drop down Menu.
- Click on authlessanonymous user and then select Portal Desktop from the View drop down list in the Navigation Frame.
- Click on the Edit link.
- Click on Manage Channels and Containers.
- Click on Edit properties of the Login Channel
- 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.
- Set the following in the AMConfig.properties file on the Portal Server host:
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
Deprecated Features
The NetMail application is being deprecated in this release of the Sun Java System Portal Server product.
Documentation Updates for Portal Server 6 2005Q1
The following sections provide updates and additional documentation for the Portal Server 6 2005Q1 documentation set.
Portal Server Administration Guide
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:
Secure Remote Access Administration Guide
The following items are not documented in the online help or Sun Java System Portal Server 6 2005Q1 Secure Remote Access Administration Guide, but are part of the Access Manager administration console.
- Gateway -> Core -> Gateway Minimum Authentication Level is not documented in the online help or the administration guide.
- The Proxylet rules (as shown on the Access Manager console) are not documented in the online help or the administration guide. For information on configuring Proxylet rules, see Proxylet Rules.
Enabling Basic HTTP Authentication
- Log in to the Access Manager administration console as administrator.
- Select the Service Configuration tab.
- Click the arrow next to Gateway under SRA Configuration.
- The Gateway page is displayed.
- Select the gateway profile for which you want to set the attribute.
- The Edit Gateway Profile page is displayed.
- Click the Core tab.
- Select the Enable HTTP Basic Authentication checkbox to enable HTTP basic authentication.
- Click Save to record the change.
- Restart the Gateway from a terminal window:
gateway-install-root/SUNWps/bin/gateway -n gateway-profile-name start
Proxylet Rules
A Proxylet rules field has been added to the Access Manager administration console.
The Proxylet rules specify the domain and proxy settings in the Proxy Auto Configuration (PAC) file.
To modify the Proxylet rules, do the following:
- Log in to the Access Manager administration console as administrator.
- Select the Identity Management tab.
- Select Organizations from the View drop-down list.
- Click the required organization name. The selected organization name is reflected as the location in the top left corner of the administration console.
- Select Services from the View drop-down list.
- Click the arrow next to Proxylet under SRA Configuration.
- Click Edit.
- Enter the proxy-host and proxy-port, using the following syntax:
[Protocol:]Domain1[,Domain2,...]:IP or Host:Port
where,
Protocol – can contain http/ftp/https. (This field is optional).
Domain – is any domain such as sun.com. Multiple domains are separated by a comma.
IP – is the IP address of the domain.
proxy-host – proxy server used for this domain(s)
proxy-port – proxy server port
The following special constructs allow dynamic insertions into the rule.
If a rule contains the string proxylet-host:proxylet-port as the proxy server, then the generated PAC file replaces the string with the host and port of Proxylet.
Online Help
The Search channel Help page states in the Advanced Search section:
The Is and Begins with operators are no longer used.
Known Issues and LimitationsThis section contains a list of the known issues with Portal Server 6 2005Q1. The following product areas are covered:
Installation
Gateway redirection not happening in any multi-session installation. (#4971011)
Regardless of the installation mode, gateway redirection does not occur during a multi-session installation.
Workaround
- Launch a Portal Server browser and access the amconsole.
- Under “Service Configuration” tab, select “gateway.”
- In the lower right corner of the window, click the “default” and the “security” tab.
- 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.
- 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)
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.
Workaround
To point to a new admin server, perform the following steps:
Configurator
The Portal Server configurator does not work if Identity Server is running its Directory Server in LDAPS. (#5044585)
Workaround
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)
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.
Workaround
Use the psconfig script as an alternative.
PortalServer-base/SUNWPs/lib/configurator script is a symlink for the PortalServer-base/SUNWPs/lib/psconfig script.
Upgrade
Netlet is not working after Upgrade from Java Enterprise Server 2 to Java Enterprise Server 3. (#6202006)
After upgrading from Java Enterprise Server 2 to Java Enterprise Server 3, the Netlet applet does not load.
Workaround
Perform the following steps from your Access Manager console to configure Proxylet and Netlet service
- Log in to the Access Manager console.
- Remove Proxylet and Netlet services.
- Choose the Identity Management tab
- Choose Services.
All the registered services are listed on the left panel.
- From SRA Configuration, select Proxylet and Netlet checkbox.
- Scroll to the top on the left panel and click the Remove button. This will remove the Proxylet and Netlet service from the ORG level.
To Verify this step manually, you may check your LDAP directory (under your orgainization) to make sure that the services (srapProxylet, srapNetlet) are really removed.
- Add the services again. To add:
- Click on the newly added services and build the template file. Click the Save button.
- Add /portal/netlet/jnlpclient.jar and /portal/netlet/netletjsse.jar to the non-Authenticated list of URLs under the gateway service. To add:
- Click the Service Configuration tab.
- Click the Gateway link under SRA Configuration. All the available gateway profiles are listed.
- Choose a particular profile by clicking on the link.
- Choose the Security tab.
- Add /portal/netlet/jnlpclient.jar in the edit field under Non-authenticated URLs and click the Add button.
- Add /portal/netlet/netletjsse.jar in the edit field under Non-authenticated URLs and click the Add button.
- Click the Save button at the bottom of the page.
- Restart your gateway server.
When upgrading from Sun Java Enterprise 2 to Sun Java Enterprise 3, no patch is available for JWSDP components upgrade. (#6202919)
Workaround
Add the following patches for the following components:
118605-01 – for SUNWjaxp
118661-01 – for JAX-RPC
118663-01 – for JAXB
117724-09 – for NSS/JSS/NSPR (sparc)
117725-09– for NSS/JSS/NSPR (x86)
Modification needed for 118128 patch readme. (#6218083)
The patch README for patch 118128 says:
Patch 117725 patch is for Solaris x86 not for Linux.
After an upgrade on the Linux platform, common hosts can not be added in NetFile. (#6218847)
After installing Java Enterprise Server 2 and then running the upgrade script, common hosts added to the NetFile service in the administration console can not be viewed in the NetFile Java2 applet.
Workaround
None.
Not able to upload file in NetFile Java1 with host type as ftp. (#6218924)
After an upgrade on the Linux and x86 platforms, files can not be uploaded using NetFile Java1.
Workaround
None.
Upgrade from Portal Server 6.3 to Portal Server 6.3.1 on the Linux platform with Sun Java System Application Server results in Anonymous Login. (#6219376)
After upgrading from Portal Server 6.3 to Portal Server 6.3.1 on the Linux and X86 platforms with Application Server the cookieless feature does not work. The Anonymous Login page is displayed instead of the Portal user’s desktop.
If you are running in the “cookies supported” mode, the desktop is displayed correctly on the Linux and X86 platforms.
Workaround
None.
When you upgrade from Java Enterprise System 2 to Java Enterprise System 3, the default Proxylet domain is not shown. (#6230842)
After the upgrade process from Java Enterprise System 2 to Java Enterprise System 3, the default Proxylet domain is not shown in the Proxylet edit rules window.
Workaround
After you run the upgrade script, delete the proxylet service and recreate the template. The recreated template will contain the default Proxylet domain component.
Migration
Import fails if the Directory Manager password is different from the Identity Server admin password. (4955769)
If the Directory Manager password provided during install is different from the Access Manager (amadmin) password, the import process during migration fails.
This is true for all migration scripts for Open Portal as well as SRA.
For running amadmin commands to modify the LDAP data, the Directory Manager password is used in the migration scripts.
This problem does not occur if the Directory Manager password and the Access Manager password are the same.
Workaround
None.
Proxylet
iNotes and Microsoft Exchange 2000 SP3 are not supported with Proxylet. (no issue ID)
Page can not be displayed in iNotes when performing some functionalities. (#6190570)
An error occurs with a message “Page cannot be displayed” in iNotes for the following modules:
This message occurs when using the Save and Delete buttons.
Workaround
None.
NetFile help does not come up after Proxylet is downloaded. (#6180420)
If Proxylet and NetFile are downloaded, the NetFile Help is not displayed and an exception is thrown in the Java console.
Workaround
None.
Unable to access the Portal Desktop in SSL mode after Proxylet is downloaded. (#4990035)
The Portal Desktop can not be downloaded after Proxylet is downloaded if Portal Server is in SSL mode.
Workaround
None.
No help provided for the Proxylet rules. (#5107957)
See Documentation Updates for Portal Server 6 2005Q1 for instructions on configuring Proxylet rules.
Accessing amconsole for a user from Proxylet gives “Action cancelled” page. (#6190566)
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.
Workaround
None.
Portlet
The portlet session is not stored across managed servers in a cluster. (#6190600)
HTTP session failover for portlets doesn’t work.
Workaround
None.
WSRP
Can not create a new WSRP Consumer Producer. (#6202285)
Creating a new WSRP consumer producer causes a server error.
Workaround
When WSRP is used with Java Enterprise System 3, 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.
Online Help
The Online Help button for the Address Book channel is missing. (#6193284)
The “Help” icon for AddressBook channel displays a “page not found” exception in the Browser.
Workaround
None.
The Portal Server Online Help links are broken in an Identity Server-Portal Server separated environment. (#6197755)
This problem occurs when Portal Server is installed on the web containers, IBM WebSphere, and BEA WebLogic.
Workaround
For BEA WebLogic
For Websphere
Communication Channels
The Mail Channel does not display the login page. (#4873659)
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.”
Workaround
Set the ipsecurity setting of the Messaging Server to “no.”
The MailProvider will not work with SSL secured IMAP. (#4919693)
The current MailProvider implementation will not work with SSL secured IMAP.
Workaround
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:
A newly created Address Book channel does not appear on the Desktop.(#4922220)
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.
The Calendar channel will not launch if the domain name is not set. (#4946959)
If the Server name in the Calendar channel does not include the fully qualified domain name, the Calendar channel does not launch.
Workaround
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)
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
Workaround
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.
The links in the Mail channel lead to the Portal Desktop instead of the Mail Client. (#5053733)
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).
Workaround
If this problem occurs, perform the following steps:
If you want a webmail login page after a logout (instead of the Portal desktop) do the following.
- 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().
Change the first line and provide the url of the mail server login page as follows:
var ref = window.document.referrer != ’’ ? "http://pavoni:2080" : ’/’
- Restart the mail server.
- Clear the browser cache.
To test:
On clicking on the Launch Mail Link of UWC Mail Channel does not open MailBox. (#6179802)
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:
The SSO adapter configuration is sunUWCMail and the SSO adapter template is SUN-UWC-MAIL.
Workaround
To use the new UWCMail channel, add the UWCMail channel to a container for the channel to be visible on the desktop.
The calendar does not come up on the UWC Calendar Channel. (#6179806)
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:
The SSO adapter configuration is “sunUWCCalendar” and the SSO adapter template is “SUN-UWC-CALENDAR.”
Workaround
To use this new channel:
Add the UWCCalendar channel to a container for the channel to be visible on the desktop.
UWC Address Book is not being displayed on the UWC AddressBook channel. (#6179807)
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.
Workaround
You can workaround this problem by doing one of the following:
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:
- Log in to the Access Manager Administration console.
- Select Service Configuration.
- Select SSO adapter.
- Select Edit Properties... for SUN-UWC-ADDRESS-BOOK.
- Select New Merge and specify:
Name: port
- Select Create.
- Select Finished.
- Select Identity Management.
- Select the organization.
- Select Services.
- Select SSO adapter.
- Select Edit Properties... for sunUWCAddressBook and specify the properties.
- 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)
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.
Workaround
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:
Lotus Address Book and Calendar does not work with old NCSO.jar. (#6216069)
Lotus Address Book and Calendar need the latest version of NCSO.jar to work.
Workaround
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)
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.
Workaround
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)
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.
Workaround
None.
Gateway
The mkchroot does not work for the gateway. (#5046586)
When running ./mkchroot, all the environment variables are shown on the console. The script then fails at the first step after providing chroot directory. This problem occurs only on the Linux platform.
Workaround
None.
Can not login to Portal Server through the gateway when Portal Server components are in separate sessions. (#6214635)
The problem occurs when Portal Server components are installed in separate sessions.
Workaround
When you add Portal Server services in separate sessions, ensure that:
After stopping and starting the Application Server, users can not log in through the Gateway. (#6191449)
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.
Workaround
Stop and restart the gateway. In a terminal window, type:
gateway-base/bin/gateway stop
gateway-base/bin/gateway start
NetFile
A local file can not be opened in NetFile. (#5033644)
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.
Workaround
None.
Adding a share in NetFile with the type “FTP,” causes an exception. (#5053765)
Users can not add an ftp share in NetFile Java1 or Java2. This problem occurs on the Linux platform.
Workaround
Make sure that ifconfig is added to the system’s search PATH.
NetFile for NFS does not work on Linux 2.1. (#6200718)
NetFile Java1 nor Java2 can access an NFS server shared mount on the Linux 2.1 platform.
Workaround
To use NetFile to access and NFS server shared mount, perform the following manual steps.
For BEA WebLogic:
For Sun Java System Application Server:
For Web Server:
Netlet
Netlet fails to load after relogin. (#2102626)
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.
Workaround
Close the browser and open a new browser to load it again.
Microsoft Internet Explorer crashes while Loading Netlet with Default Microsoft JVM. (#2120110)
When Netlet is loading, a security message is displayed. Clicking “yes” to continue causes Microsoft Internet Explorer to crash.
Workaround
None.
Netlet does not work if a Pac file is specified in the browser option with Java 1.4.2. (#6204073)
This problem can happen if the plug-in is not able to understand the format in which the pac file location is specified.
Workaround
The format for the location of pac file needs to be specified for various versions of Java.
Rewriter
When using Microsoft Exchange 2003, gif files are missing in some of the pages. (#6186547)
Many interface image files are missing.
Workaround
None.
In iNotes, under the Contacts tab, the Help page is redirected to the Administration console. (#6186541)
Clicking the Help button from the Contacts tab in iNotes displays the Administration console page instead of the Help page.
Workaround
None.
iNotes does not logout correctly. (#6186544)
Clicking on logout in iNotes displays two options. Neither of these options will log out of iNotes.
Workaround
None.
Microsoft Exchange 2000 SP3 gives warning messages and action cancelled messages. (#6186535)
The following actions in Exchange 2000 SP3 it causes security warning messages and Action cancelled messages:
Workaround
None
Microsoft Exchange 2003 returns a login page when clicking on the Calendar reminder page on the “open item” button. (#6186528)
Workaround
None
When using Microsoft Exchange 2000 SP3, Moving or Copying messages to specific folders doesn’t work. (#6186534)
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.”
Workaround
None.
When using Microsoft Exchange 2000 SP3, selecting any item in the drop box list gives Action Cancelled message. (#6186533)
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.
Workaround
None.
When using Microsoft Exchange 2000 SP3, Clicking on empty deleted items folder displays Action Cancelled. (#6186540)
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.
Workaround
None.
Documentation
Chapter 9 of the Sun Java System Portal Server 6 2005Q1 Secure Remote Access Administration Guide contains an inaccurate title for subsection. (no issue ID)
The subsection “Enable Rewriting of All URLs” should read “Enable Rewriting of All URIs.”
Missing line in the instructions for running the configurator in a localized environment for Solaris Sparc or X86 machines. (#6238677)
Chapter 2 of the Sun Java System Portal Server 6 220Q1 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 18 of the Sun Java System Portal Server 6 2005Q1 Administration Guide contains the wrong path for the desktopconfig.properties file. (no issue ID)
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)
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
The rewriter documentation should state that only http and https are supported. (#5082368)
The section “Supported URLs” in chapter 12 “Administering the Rewriter Service” of the Sun Java System Portal Server 6 2005Q1 Administration guide states that “Rewriter supports rewriting of all standard URLs as specified by RFC-1738.” This information is incorrect. Rewriter supports only HTTP and HTTPs URLs.
Workaround
None.
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)
Workaround
None.
Mail is sometimes displayed as HTML document. (4938743)
Email messages sent with HTML in the body are displayed with the HTML source.
Workaround
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:
For the Outlook Express client:
The default value shown in the Document Root Directory of the Portal Server Configuration Panel during JES installer is incorrect. (6203728)
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.
Workaround
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)
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.
Workaround
None.
The Views: Rule for Date Contains does not work. (6212818)
Date search using a string format as dd/mm/yyyy in the search filter will not work.
Workaround
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)
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.
Workaround
Do not use leading or trailing spaces in view and rule names.
URL forwarding to minimize URL length for mobile and desktop users. (5020380)
URL forwarding will be required to minimize URL length for desktop and phone users.
Workaround
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 fixed 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)
Workaround
None.
Using Application Server 7.1 UR1 in the cookieless mode. (#5107310)
Workaround
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)
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.
Workaround
None.
Web server always sets content type to text/html when servlet filter is set. (#6174754)
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.
Workaround
Make the following change to the obj.conf file in web-server-instance/config directory.
Changing client type in palmOne Treo 180 device to cHTML. (#6190070)
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.
Workaround
The following steps will enable you to change the client type to cHTML using amconsole:
- Navigate your browser to http://hostname:port/amconsole.
- Login as an administrator.
- Click on Service Configuration tab -> Client Detection -> Client Types: Edit (on the right panel).
The Client Manager is displayed.
- Select the WML category to get the list of WML capable devices.
- Edit UPG1_UP_4.0_(compatible__Blazer_1.0) and change the “Immediate parent type for this device” to cHTML.
- 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)
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.”
Workaround
None.
Views menu option from mail is not displayed on Mobile desktop. (#6185041)
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.
Workaround
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.
- Navigate your browser to http://hostname:port/amconsole.
- Login as an administrator.
- Click on Users -> click a user -> Services -> Portal Desktop -> Edit -> Edit XML directly.
- Locate the <Collection name="selectedClients"> tag.
This tag lists all the selected client devices.
- Add the following tag:
<String name="_http___developer.openwave.com_uaprof_OPWVSDK62.xml_" value=""/>
- Save your changes.
- Login to the Portal Desktop as an User.
- New mobile device called
_http___developer.openwave.com_uaprof_OPWVSDK62.xml_ displays.
- Attach a new mail view to this device.
- Login using the Openwave 6.2 (xhtml) simulator.
- 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)
When users access Mobile Mail Preferences link by clicking Edit Mail from the Portal Desktop, no help is displayed for Mobile Mail Preferences.
Workaround
None.
Devices rendering HDML content display garbage for Japanese characters for detail pages for Calendar, Mail, and Address Book. (#6191363)
When users view their Calendar, Mail, and Address Book the content gets corrupted for Japanese locale when viewing HDML content. For example, when users:
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.
Workaround
None.
Mail and calendar events sent in Japanese from browser, and then viewed on handset are corrupted and vice versa. (#6191389)
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.
Workaround
None.
Portal Server Mobile Access Upgrade Files are Updated (no issue ID)
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
The date and time are not displayed according to the locale in the Calendar. (#4971337)
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.
Workaround
None.
Reminder time for Calendar task does not accept modification. (#5031431)
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.
Workaround
None.
The Date in NetFile depends on locale of the server. (#5026281)
The date format should depend on the user’s locale not the server’s locale.
Workaround
None.
Chinese text file attachment can not be saved correctly in Netmail. (#5031446)
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.
Workaround
None.
Unzipping a multibyte file in which the filename is a multibyte filename causes the filename to get corrupted. (#5033641)
If a multibyte file that has a multibyte filename is unzipped the filename gets corrupted.
Workaround
None.
The naming order of address book entries is strange for Japanese users. (#6197714)
The address book channel and map address book displays first name then last name. It should display last name, then first name.
Workaround
None.
When using Netmail Lite to send mail in Japanese, the end of the message displays either question marks or garbage charaters.(#6197737)
Workaround
None.
When using the de_DE locale, the advanced search page is incorrect. (#6208359)
After clicking the search tab, the advanced search page comes up but part of the page is missing.
Workaround
None.
The Proxylet (under Secure Remote Access) configuration page in the Administration Console is not localized. (#6208800)
Workaround
None.
The edit page of the Instant Messaging Channel displays an error page. (#6210507)
Clicking the edit button of the Instant Messaging channel causes an error page to be displayed.
Workaround
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)
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.
Workaround
None.
Clicking on the “Edit” button of a channel with a multibyte name causes an empty page to be displayed. (#6193860)
Workaround
None.
Can not post a note in the Notes channel.(#6193889)
Portal desktop users are unable to post a note in Notes Channel because the channel can not be edited.
Workaround
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)
For Japanese users, the time format on calendar channel should be PM: HH:MM - AM: HH:MM.
Workaround
None.
Users can not cancel the Netlet warning dialog box. (#2112878)
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.
Workaround
None.
Instant Messenger can not be invoked as Java Web start style in with some JDK versions. (#6199908)
This problem occurs when the user tries to access the Portal Server desktop on a Windows machine with J2SE 1.5.0 installed.
Workaround
None.
Unable to send mail using NetFile Java1. (#4910252)
Files can not be sent using the mail button from NetFile Java1, when file path or file name contains multi-byte characters.
Files can be mailed using NetFile Java2.
Workaround
None.
The date format specified in the Netmail Online Help is wrong. (#4920181)
The Netmail Online Help states that the date format to search for mail is mm-dd-yy. This format is incorrect in many locales.
Workaround
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)
The date format used is Month Day, Year. The format should be Day Month Year.
Workaround
None.
Events in the Calendar channel use the wrong time format for European locales. (#5033735)
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.
Workaround
None.
The Korean version of Netmail’s Find application does not locate all messages properly. (#5036419)
The before/on option does not highlight messages that match the on value. The after/on option highlights messages that match the on value.
Workaround
None.
For simplified Chinese users, the default language in the User Information channel’s editing page is English. (#5036625)
The locale XML files are set for en, not zh.
Workaround
None.
The Anonymous desktop (/portal/dt) is not displayed according to the preferred language set in the browser. (#5059646)
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.
Workaround
None.
When languages are selected, configuration of localization is slow. (#5074720)
Portal Server software configuration requires several minutes for each language. Each language uses many XML files, and dpadmin is called for each.
Workaround
None.
Localized authentication JSPs for Portal Server Mobile Access are not deployed into the Access Manager. (#6191601)
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.
Workaround
None.
Portal Server May Not Deploy for Spanish Locale. (#6214289)
Portal Server may not start when deployed with Sun Java System Web Server if Portal Server was installed using the text-based interface.
Workaround
None.
NetFile Does Not Correctly Display Windows 2000 Shared Folder Names for Japanese Locale. (#6215099)
The folder name is displayed as garbage only for the Japanese locale.
Workaround
None.
Redistributable FilesSun Java System Portal Server 6 2005Q1 does not contain any files which you can redistribute.
How to Report Problems and Provide FeedbackIf you have problems with Sun Java System Portal Server, contact Sun customer support using one of the following mechanisms:
- Sun Software Support services online at
http://www.sun.com/service/sunone/softwareSo that we can best assist you in resolving problems, please have the following information available when you contact support:
- Description of the problem, including the situation where the problem occurs and its impact on your operation
- Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
- Detailed steps on the methods you have used to reproduce the problem
- Any error logs or core dumps
If you have problems with Sun Java System Portal Server, Mobile Access, please have the following information available when you contact support:
- Description of the problem, including the situation where the problem occurs and its impact on your operation
- Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
- Detailed steps on the methods you have used to reproduce the problem
- What patches (with patch numbers) are installed
- Whether the problem is seen on the phone, the emulator, or Mobile Access server
- Whether the problem is specific to any particular type of device (for example, Sony Ericsson P800 or Nokia 3650)
- Whether problem occurred on default installation of Mobile Access software (if applicable)
- When the problem was first seen
- Whether the problem occurs all the time or randomly
- What changes, if any, were made just before the problem started
- How many users are affected by the problem
- The number instances of Mobile Access software and how they are linked to Portal Server software and Access Manager software
- The number of machines and how they are set up with regard to Mobile Access software
- What error messages or exceptions are reported in the log files under /var/opt/SUNWps/debug or /var/opt/SUNWam/debug
- What error messages are reported in the information window for emulators
- What the web server port is where Mobile Access is installed
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:
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 817-7699.
Additional Sun ResourcesUseful Sun Java System information can be found at the following Internet locations:
- Sun Java System Documentation
http://docs.sun.com/prod/sunone- Sun Java System Professional Services
http://www.sun.com/service/sunps/sunone- Sun Java System Software Products and Service
http://www.sun.com/software- Sun Java System Software Support Services
http://www.sun.com/service/sunone/software- Sun Java System Support and Knowledge Base
http://www.sun.com/service/support/software- Sun Support and Training Services
http://training.sun.com- Sun Java System Consulting and Professional Services
http://www.sun.com/service/sunps/sunone- Sun Java System Developer Information
http://sunonedev.sun.com- Sun Developer Support Services
http://www.sun.com/developers/support- Sun Java System Software Training
http://www.sun.com/software/training- Sun Software Data Sheets
http://wwws.sun.com/software
Copyright � 2005 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
SUN PROPRIETARY/CONFIDENTIAL.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms.
This distribution may include materials developed by third parties.
Portions may be derived from Berkeley BSD systems, licensed from U. of CA.
Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.
Copyright � 2005 Sun Microsystems, Inc. Tous droits r�serv�s.
Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plus des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.
Propri�t� de SUN/CONFIDENTIEL.
L'utilisation est soumise aux termes du contrat de licence.
Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.
Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.
Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.