Sun Java™ System Portal Server 6.2 Release Notes for Windows

Version 6.2 May 2004

817-7366-10

These release notes contain important information available at the time of release of Version 6.2 of Sun Java™ System Portal Server software. New features and enhancements, known limitations and problems, technical notes, and other information are addressed here. Read this document before you begin using Portal Server 6.2.

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/prod/sunone. 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 manuals.

These release notes contain the following sections:

About Portal Server, Version 6.2
Installation Notes
Post-Installation Notes
Known Issues
How to Report Problems and Provide Feedback
Additional Sun Resources

---

About Portal Server, Version 6.2

Sun Java System Portal Server software provides a platform to create portals for your organization’s integrated data, knowledge management, and applications. The Portal Server software platform offers a complete infrastructure solution for building and deploying all types of portals, including business-to-business, business-to-employee, and business-to-consumer.

---

Installation Notes

This section contains the following:

Hardware Requirements
Operating System Requirements
Software Requirements
Browser Recommendations
Instructions for Installing Sun Java System Portal Server Software
Instructions for Uninstalling Portal Server Software

Hardware Requirements

Table 1  Hardware Requirements 

Component	Windows Requirement
CPU	500 Mhz
RAM	256 Mbytes
Disk space	30 Mbytes for Portal Server and associated applications

Operating System Requirements

The Portal Server software requires Windows 2000 Professional, Windows-XP Professional 2002, or Windows 2003 Professional operating system.

Software Requirements

The Portal Server software requires the following software components. Install these software components before installing the Portal Server software. You will be required to supply the parameters outlined in Table 4 when installing Portal Server software. So, when installing these software, make a note of the Value Used During Installation for the corresponding Parameter outlined in Table 4.

Java™ Development Kit version 1.4.1_01    

The Portal Server software supports 1.4.1_01 version of the JDK software.

Sun Java System Web Server 6.1    

Download and install 6.1 version of the Web Server software. See http://docs.sun.com/817-1830-10/win.html for detailed installation instructions.

Sun Java System Application Server 7.0 MU 1    

Download and install 7.0 MU 1 version of the Application Server software. See http://docs.sun.com/source/817-2169-10/igdevops.html for detailed installation instructions.

Sun Java System Directory Server 5.2    

Remove all previous versions of the software. Download and install 5.2 version of the Directory Server software. See http://docs.sun.com/db/doc/816-6697-10?q=816-6697-10 for detailed installation instructions.

Sun Java System Identity Server 6.1    

The Portal Server software will install 6.1 version of the Identity Server software. To install the Identity Server software, modify the values for the parameters listed in is_statefile_webserver (for installation on Web Server) or is_statefile_appserver (for installation on Application Server) and is_statefile_sdk (for SDK only installation).

Before modifying the parameters:

Save a copy of the sample state files.
Do not manually create the statefile. Only edit the given sample statefiles.
Do not modify parameters, except to edit their values.
Do not remove a parameter, even if it does not have a value.
Do not add a parameter.
Do not change the order of the parameters.
When editing the values, make a note of the original type and format and maintain them as you enter the new value. For example:
If the old value is a host name, enter a host name and not a fully qualified domain name.
If the old value starts with a leading slash, make sure that the new value starts with a leading slash.
Retain the case of the original value
Replace any value that you delete. Do not leave any blank parameters by deleting the value of the paramater in the sample statefile. Those parameters which already have some value in the sample statefile are mandatory fields and they must have some value, otherwise installation or configuration could fail.
Do not modify or delete the statefile id tags: [STATE_BEGIN Sun ONE Identity Server 1ad7c58f9e25307e25fc3494818c65762b8252e0] and [STATE_DONE Sun ONE Identity Server 1ad7c58f9e25307e25fc3494818c65762b8252e0].

Code | Figure | Table and Table 3 lists the parameters in the sample statefiles in the first column, provides a brief description of the parameter in the second column, includes the default or sample value in the third column, and specifies whether or not the parameter’s value is editable in the fourth column.

Table 2  is_statefile_webserver  

Parameter	Description	Sample or Default Value	Editable?
NETWORK_DOMAIN	Domain of the network	For example, subdomain.example.com	Yes
QUICK_INSTALL	Quick installation without input of a lot of system settings	false	No
installType	System setting for quick installation	default	No
com.iplanet.am.installer.panels.ComponentPanel.selectedcomponents	The Identity Server component to install	SunONEIdentityServerManagementandPolicyServices	No
SDK_ONLY_INSTALL	Install the Identity Server software SDK package only	false	No
defaultInstallDirectory	Default installation directory	C:\Program Files\Sun\IdentityServer6	No
currentInstallDirectory	Preferred directory to install the Identity Server software	For example,	Yes
DSAME_PORT	Identity Server software port	For example,	Yes
CUSTOM_JDK	Use existing JDK	true	Yes
IS_PROTOCOL	Identity Server protocol	http	Yes
IWS_INSTALL	Web Server is already installed	false	No
CDS_HOST	Fully qualified host name	For example, hostname.subdomain.example.com	Yes
CDS_WSDIR	The web server instance directory	C:\ws61_install\https-hostname.subdomain.example.com	Yes
CDS_PORT	Web instance port	For example, 80	Yes
CDS_PROTOCOL	CDS deployment protocol	http	Yes
CDS_DEPLOY_URI	CDS deploy URI like amcommon	For example, amcommon	Yes
JAVA_COMPONENT_PACKAGES	Java package has to be installed	true	No
DSAME_SERVER	Fully qualified host name	For example, hostname.subdomain.example.com	Yes
DSAME_HOST	The host name	For example, satin	Yes
DSAME_PROTOCOL	Identity Server protocol	http	Yes
DSAME_DEF_DOMAIN	Defdomain	For example, example.com	Yes
DSAME_FULL_DOMAIN	Full domain	For example, subdomain.example.com	Yes
DSAME_SUB_DOMAIN	subdomain	For example, subdomain	Yes
DEFAULT_ORG1	Default organization; same as Defdomain	For example, example.com	Yes
SERVER_DEPLOY_URI	Uniform Resource Identifier (URI) prefix for accessing the HTML pages, classes, and JAR files associated with the Identity Management and Policy Services Core subcomponent. The default value is amserver. Do not enter a leading slash.	amserver	Yes
EXIST_DIT_SCHEMA	Use existing DIT and schema	false	Yes
ADMIN_COMPONENT_SELECTED	Admin component selected for installation	true	No
CONSOLE_DEPLOY_URI	URI prefix for accessing the HTML pages, classes and jars associated with the Identity Server Administration Console subcomponent.The default value is amconsole. Do not enter a leading slash.	amconsole	Yes
PASSWORD_SERVICE_DEPLOY_URI	URI that determines the mapping that the web container running Identity Server will use between a string you specify and a corresponding deployed application. The default value is ampassword. Do not enter a leading slash.	ampassword	Yes
CONSOLE_OVER_SERVICES	Remote console if the value is false	true	No
COOKIE_DOMAIN_LIST	The names of the trusted DNS domains that Identity Server returns to a browser when it grants a session ID to a user.You can scope this value to a single top-level domain, such as example.com. The session ID will provide authentication for all subdomains of example.com. Alternatively, you can scope the value to a comma-separated list of subdomains, such as .corp.example.com,.sales.example.com. The session ID will provide authentication for all subdomains in the list. A leading dot (.) is required for each domain in the list. The default value is the current domain, prefixed by a dot (.). Leave it blank if the hostname is not a fully qualified domain name.	For example, .example.com	Yes
DSAME_CONSOLE	Fully qualified domain name for the server hosting the existing console. The default value contains the value that you provided for Host (DSAME_CONSOLE_HOST), a dot, and then the value of the full domain.	As an example, if the host is satin and the domain is example.com, the default value is satin.example.com.	Yes
DSAME_CONSOLE_HOST	Host name	For example, satin	Yes
CONSOLE_PROTO	Protocol for the admin console	http	Yes
DSAME_CONSOLE_PORT	Port on which Web/Application Server listens for HTTP connections.	80	Yes
DSAME_CONSOLE_DEF_DOMAIN	Identity Server console default domain	For example, example.com	Yes
DSAME_CONSOLE_FULL_DOMAIN	Identity Server console full domain	For example, subdomain.example.com	Yes
DSAME_CONSOLE_SUB_DOMAIN	Identity Server console sub domain	For example, subdomain	Yes
USE_DSAME_SERVICES_WEB_CONTAINER		1	No
DIT_COMPLIANCE	See Identity Server Deployment Guide for more information	false	Yes
DEFAULT_ORG1	Default organization; same as DSAME_CONSOLE_DEF_DOMAIN	For example, example.com	Yes
DS_ALREADY_EXISTS	Directory Server already exists	true	No
LOAD_DIT	See Identity Server Deployment Guide for more information	y	No
AUTO_LOAD	Auto load the DIT	y	No
CUSTOM_DIRECTORY	Directory Server already exists	true	No
DS_SERVER	A host name or value that resolves to the host on which Directory Server resides. The default value is the fully qualified domain name of the local machine.	For example, if the local machine is satin.example.com, the default value is satin.example.com.	Yes
DS_HOST	Directory Server hostname	For example, satin	Yes
DS_PORT	Port on which Directory Server listens for client connections.	389	Yes
DS_ROOT_DN	DN of the user who has unrestricted access to Directory Server.	cn=Directory Manager	Yes
DS_ROOT_PASSWD	Password for the directory manager.	For example, admin123	Yes
LOCAL_IDS		true	Yes
LOAD_SCHEMA	Load the schema	true	Yes
DS_ROOT_SUFFIX	Distinguished name (DN) to set as the Identity Server root suffix.The default value is based on the fully qualified domain name for this host, minus the host name.	For example, if this host is satin.subdomain.example.com, the value is dc=subdomain,dc=example,dc=com	Yes
LDAPUSER	Bind DN user for LDAP, Membership, and Policy services. This user has read and search access to all Directory Server entries.	amldapuser	No
LDAPUSERPASSWD	Password of the amldapuser user. This password must be different from the password of the amadmin user. It can be any valid Directory Service password.	For example, 11111111	Yes
SUPERADMIN	Identity Server top-level administrator. This user has unlimited access to all entries managed by Identity Server software. The default name, amadmin, cannot be changed. This ensures that the Identity Server administrator role and its privileges are created and mapped properly in Directory Server, allowing you to log onto Identity Server immediately after installation.	amAdmin	No
SUPERADMINPASSWD	Password of the amadmin user. The value must have at least eight characters.	For example, admin123	Yes
AM_ENC_PWD	Encryption for Identity Server admin password	YyonjmRltd0XoaA/AJ/ReQYEkBJj9ZkJ	Yes
DEPLOY_SERVER	Web container to deploy Identity Server	SUN_WEBSERVER	Yes
JDK_PATH	Path to JDK	C:\j2sdk1.4.2_02	Yes
JDK_BASE_DIR	JDK base directory	C:\j2sdk1.4.2_02	Yes
WSDIR	Directory where web server is installed.	C:\ws61_install	Yes
WS_INSTANCE	Web Server instance	https-Satin.subdomain.sun.com	Yes
CDS_BASE_WSDIR	Directory where web server is installed.	C:\ws61_install	Yes
DOCS_DIR	Directory where Web Server stores content documents.	C:\ws61_installdocs	Yes

Table 3  is_statefile_appserver  

Parameter	Description	Sample or Default Value	Editable?
DEPLOY_SERVER		SUN_APPSERVER	No
SUNAPPSERVER_INSTALL_DIR	Path to the directory where Application Server is installed.	C:\Sun\jstudio\AppServer7	Yes
SUNAPPSERVER_ADMIN	User ID of the Application Server administrator.	admin	Yes
SUNAPPSERVER_PORT	Port on which the Administration Server for Application Server listens for connections.	4848	Yes
SUNAPPSERVER_PASSWORD	Password of the Application Server administrator.	For example, 11111111	Yes
SUNAPPSERVER_DOMAIN		domain1	Yes
SUNAPPSERVER_INSTANCE	Name of the Application Server instance that will run Identity Server.	server1	Yes
SUNAPPSERVER_INSTANCE_DIR	Path to the directory where Application Server stores files for the instance.	C:\Sun\jstudio\AppServer7\domains\domain1\server1	Yes
SUNAPPSERVER_CONFIG_DIR	Path to the directory that contains the configuration files for the instance of Application Server.	C:\Sun\jstudio\AppServer7\domains\domain\server1\config	Yes
JDK_PATH	Path to JDK	C:\j2sdk1.4.2_02	Yes
JDK_BASE_DIR	JDK base directory	C:\j2sdk1.4.2_02	Yes
AS_ADMIN_PROTOCOL	Application Server admin protocol	http	Yes
SUNAPPSERVER_DOCS_DIR	Directory where Application Server stores content documents.	C:\Sun\jstudio\AppServer7domains\domain1\server1\docroot	Yes

After installing the Identity Server software:

For Web Server deployments, stop the web server instance and the web server administration server instance.
For Application Server deployments:
Access the admin console at http://hostname:4848.
In the left frame click on the key to the left of App Server Instances, select the application server instance on which Identity Server was installed
Click apply changes and then stop the application server instance.
For Web Server deployments, start the web server administration server instance and then start the web server instance.
For Application Server deployments, start the application server.
Verify the installation by browsing to http://FullyQualifiedHostName:port/amconsole and logging into the Identity Server administration console.

Browser Recommendations

The following browsers are supported for administration and for accessing the Sun Java System Portal Server software Desktop:

Internet Explorer 5.5 and 6.0
Netscape™ 4.7x or higher

Instructions for Installing Sun Java System Portal Server Software

This section contains the following:

Pre-Installation Requirements
Updates to Secure Remote Access Component Installation
Installing Gateway, Netlet Proxy, and/or Rewriter Proxy on an Independent Node

Pre-Installation Requirements

Ensure that your system meets the hardware requirements outlined in "Hardware Requirements."
Install the software listed in "Browser Recommendations" on page 10 and complete the checklist in Table 4.
Ensure that the Value Used During Installation column in Code | Figure | Table for the corresponding Parameter is completed before installing Sun Java System Portal Server software.
Build the statefile.

For Identity Server, see Table 2 and Table 3. For Identity Server SDK, see Table 5.

Table 4  Installation Checklist for Sun Java System Portal Server Software Installation 

Parameter	Value Used During Installation
Web Server software BaseDir
Web Server software instance name
Web Server software document root.
Application Server software BaseDir
Application Server software administrator’s user ID and password
Application Server software administration port
Application Server software domain
Application Server software instance
Application Server software document root
Directory Server software directory manager’s DN and password
Identity Server software BaseDir
Identity Server software internal LDAP authentication user (amldapuser) password
Identity Server software administrator (amadmin) password

  To Install Portal Server Software

Log in to the system as administrator.
Restart the deployment server instance and admin.
Download the Portal Server software.
Unzip the Portal Server software.
Go to the unzipped directory and click on setup.bat.
Specify the full path to the Identity Server software statefiles to install the software using the statefiles and select Next.

See "Sun Java System Identity Server 6.1" on page 3 for more information.

Note	Identity Server install fails if the web container base directory contains spaces.

Check whether Identity Server is installed properly and then restart the deployment server. After restarting the server, access the Identity Server software administration console at http://fullyqualifiedhost:port/amconsole. If it throws an error check the install logs at Systemdriveocuments and Settings\Administrator\Local Settings\Temp.
Review the license and accept the license terms. To agree to the license terms:
Read the warning in the Welcome page and select Next.
Review the software license agreement terms and select Yes (Accept License).
Select the check box next to the Portal Server software components you wish to install.

The Portal Server software components include:

Support for Secure Remote Access to the portal server
A sample portal Desktop
A Secure Remote Access sample (this can be installed only if you install the sample portal Desktop)
Gateway
Netlet proxy
Rewriter proxy

To select the components for installation:

Select the checkbox next to the component you wish to install.
Select Next.
Specify the directory where you wish to install the Portal Server software components.

Note that this will be referred to as the Portal Server software BaseDir throughout this document. Also note that Portal Server install fails if the directory name contains spaces. To specify:

Select (by selecting the Browse button) or type the directory in the text field.

By default, the Portal Server software is installed in C:\Sun\PortalServer6.

Select Next.
Specify the following deployment information and select Next.
Web container - The Portal Server software can be installed into two possible web containers. To specify the web container, select the radio button next to the appropriate web container. The selected web container must already be installed and running before installing the Portal Server software.

Note	At this time, the Portal Server software includes support for only Sun Java System Web Server and Sun Java System Application Server software.

URI - By default, the deployment URI is /portal.
Specify the web container information and select Next. That is:
If you are deploying on a web server, specify the web server software BaseDir, instance name, and document root.
If you are deploying on Sun Java System Application Server, specify the application server software BaseDir, domain, instance name, document root directory, administrator’s name and password, and the administration port number.
Specify the Identity Server software information and select Next. That is, provide the:
Identity Server software BaseDir
Internal LDAP authentication user password
Administrator’s (amadmin) password
Directory manager’s DN and password
Specify the Secure Remote Access information and select Next.

If you are not installing the Secure Remote Access component, skip this step and proceed to the Step 19 on page 15. To install the Secure Remote Access component, specify:

Portal server domain
Gateway protocol
Gateway domain
Gateway access port number
Gateway profile name
Gateway logging user password
Specify information for installing the Gateway and select Next.

If you are not installing the Gateway component, skip Step 11 and Step 12, and proceed to Step 19 on page 15. To install the Gateway component, specify:

Gateway protocol
Hostname
Portal server domain and subdomain names
Gateway IP Address and access port number
Gateway profile name
Log user password
Whether or not to start the Gateway after installation
Specify the Gateway certificate information and select Next. That is, specify:
Whether or not to create a self-signed certificate
Your organization and division
City or locality, state or province, and two letter county code
The certificate database password
Specify the Netlet Proxy information and select Next.

If you are not installing the Netlet Proxy, skip this step and proceed to Step 19. To install the Netlet Proxy, specify:

Hostname
Portal server domain and subdomain names
Netlet Proxy IP Address and access port number
Gateway profile name
Log user password
Specify the Rewriter Proxy information and select Next.

If you are not installing the Rewriter Proxy, skip this step and proceed to Step 19. To install the Rewriter Proxy, specify:

Hostname
Portal server domain and subdomain names
Rewriter Proxy IP Address and access port number
Gateway profile name
Log user password
Review the installation summary and select Next.

If you need to make modifications, select Back.

Select Install Now to install the software.

Updates to Secure Remote Access Component Installation

The Portal Server software Netlet and Gateway components need Rhino JavaScript parser (bundled as rhino/js.jar) for PAC file support. This must be installed in the Gateway and Portal Server node. To install, copy rhino/js.jar to ${JAVA_HOME}/jre/lib/ext directory.

Installing Gateway, Netlet Proxy, and/or Rewriter Proxy on an Independent Node

To accomplish this:

Install the Identity Server software SDK.
Install the Portal Server software Gateway component.

  To Install the Identity Server Software SDK

Modify the editable parameters in the sample is_statefile_sdk file. See Code | Figure | Table for information on the parameters. Code | Figure | Table lists the parameters in the sample statefiles in the first column, provides a brief description of the parameter in the second column, includes the default or sample value in the third column, and specifies whether or not the parameter’s value is editable in the fourth column.

Table 5  is_statefile_sdk  

Parameter	Description	Sample or Default Value	Editable?
NETWORK_DOMAIN	Domain of the network	For example, subdomain.example.com	Yes
QUICK_INSTALL	Quick installation without input of a lot of system settings	false	No
installType	System setting for quick installation	default	No
com.iplanet.am.installer.panels.ComponentPanel.selectedcomponents	The Identity Server component to install	SDKComponent	No
SDK_ONLY_INSTALL	Install the Identity Server software SDK package only	true	No
DEPLOY_SERVER		SUN_WEBSERVER	No
defaultInstallDirectory	Default installation directory	C:\Program Files\Sun\IdentityServer6	No
currentInstallDirectory	Preferred directory to install the Identity Server software	C:\IS61_install	Yes
DSAME_PORT	Identity Server software port	80	Yes
JDK_PATH	Path to JDK	C:\IS61_install\java	Yes
JDK_BASE_DIR	JDK base directory	C:\IS61_install\java	Yes
CUSTOM_JDK	JDK already exists	false	No
IS_PROTOCOL	Identity Server protocol	http	No
IWS_INSTALL	Web Server already installed	false	No
JAVA_COMPONENT_PACKAGES	Install JDK package	true	No
DSAME_SERVER	Fully qualified host name of the Identity Server	For example, Satin.subdomain.example.com	Yes
DSAME_HOST	Identity Server host name	For example, Satin	Yes
DSAME_DEF_DOMAIN	Defdomain	For example, example.com	Yes
DSAME_FULL_DOMAIN	Full ldomain	For example, subdomain.example.com	Yes
DSAME_SUB_DOMAIN	subdomain	For example, subdomain	Yes
DEFAULT_ORG1	Default organization	For example, example.com	Yes
SERVER_DEPLOY_URI	Uniform Resource Identifier (URI) prefix for accessing the HTML pages, classes, and JAR files associated with the Identity Management and Policy Services Core subcomponent. The default value is amserver. Do not enter a leading slash.	amserver	Yes
EXIST_DIT_SCHEMA	See Identity Server Deployment Guide for more information	true	Yes
COOKIE_DOMAIN_LIST	Domain where cookies will be forwarded	For example, .example.com	Yes
DIT_COMPLIANCE	See Identity Server Deployment Guide for more information	false	No
DEFAULT_ORG1	Default organization	For example, example.com	Yes
DS_ALREADY_EXISTS	Directory Server already exists	true	No
CUSTOM_DIRECTORY		true	No
DS_SERVER	A host name or value that resolves to the host on which Directory Server resides. The default value is the fully qualified domain name of the local machine.	For example, hostname.subdomain.example.com	Yes
DS_HOST	Directory Server host name	For example, Satin	Yes
DS_PORT	Port on which Directory Server listens for client connections.	For example, 29745	Yes
LOCAL_IDS	Directory Server is installed locally	true	Yes
DS_ROOT_SUFFIX	Distinguished name (DN) to set as the Identity Server root suffix.The default value is based on the fully qualified domain name for this host, minus the host name.	For example, dc=subdomain,dc=example,dc=com	Yes
LDAPUSER	Bind DN user for LDAP, Membership, and Policy services. This user has read and search access to all Directory Server entries.	amldapuser	Yes
LDAPUSERPASSWD	Password of the amldapuser user. This password must be different from the password of the amadmin user. It can be any valid Directory Service password.	For example, 11111111	Yes
SUPERADMIN	Identity Server top-level administrator. This user has unlimited access to all entries managed by Identity Server software. The default name, amadmin, cannot be changed. This ensures that the Identity Server administrator role and its privileges are created and mapped properly in Directory Server, allowing you to log onto Identity Server immediately after installation.	amAdmin	Yes
SUPERADMINPASSWD	Password of the amadmin user. The value must have at least eight characters.	For example, admin123	Yes
AM_ENC_PWD	Encryption for Identity Server admin password	YyonjmRltd0XoaA/AJ/ReQYEkBJj9ZkJ	Yes

Note	The amadmin password, amladpuser password, and the encryption key used has to be the same. You can find the encryption password in the Identity Server software server at S1ISBaseDir/SUNWam/lib/AMConfig.properties files.

  To Install the Gateway

Invoke the Portal Server software installer.
Choose only the Gateway component.

Follow the instructions to "To Install Portal Server Software."

  To Install the Rewriter Proxy

Invoke the Portal Server software installer.
Choose only the Rewriter Proxy component.

Follow the instructions to "To Install Portal Server Software."

  To Install the Netlet Proxy

Invoke the Portal Server software installer.
Choose only the Netlet Proxy component.

Follow the instructions to "To Install Portal Server Software."

Instructions for Uninstalling Portal Server Software

To uninstall the Portal Server software:

Log in to the machine running the Portal Server software as administrator.
Change directories to the Portal Server software BaseDir.

The BaseDir is the software installation root directory.

Run the uninstallation.bat command.
Select Next at the welcome screen.
Specify the Web Container Administration Password and Identity Server Administration Password.
Select Next to uninstall.

The Wizard will display the progress of the uninstallation.

Instructions for Uninstalling Identity Server Software

To uninstall the Identity Server software:

Goto the directory where Identity Server is installed.
Run uninstall.bat.
Select next at the Welcome panel.
Select Full uninstallation to uninstall all the components.
Enter the directory manager name and password.

The Identity Server software will be uninstalled.

---

Post-Installation Notes

This section contains the following:

File System Layout
Log Files
Command Line Utilities

File System Layout

Log Files

Table 6  Log Files

Component	File Location
Desktop	<identity-server-install-dir>\logs
Portlet	<identity-server-install-dir>\logs
NetMail	<identity-server-install-dir>\logs
Secure Remote Access components	<portal-server-install-dir>\default\<identity-server-install-dir>\logs
Search	<portal-server-install-dir>\https-<instance-name>\portal\logs

Command Line Utilities

The following command-line utilities are available with this software:

deploy.bat	Deploys a web application in the web container.
dpadmin.bat	Enables display profile objects to be retrieved, added, modified, and removed from a display profile document.
multiserverinstance.bat
par.bat	Performs functions involving the .par file for transport of channels and/or providers.
pdeploy.bat	Deploys a portlet web application in the web container.
rdmgr.bat	Performs all the functions needed by the Search server to work with resource descriptions and the search database.
rwadmin.bat	Enables the administrator to manage the Rewriter data.
undeploy.bat	Removes the portlet application from the portal server.
sraIM.cmd	This is the gateway multi-instance script.

---

Known Issues

This section contains a list of the more important known issues at the time of the Portal Server 6.2 release. This section covers the following topics:

Features Not Available
Known Bugs

Features Not Available

The following features are not available in this version of the software:

NetFile support to NFS shares
Watchdog mechanism
Support for IBM and BEA application servers
Netlet proxy and Rewriter proxy
Rewriter proxy and Netlet proxy multiinstance script

Known Bugs

Creating gateway instance by executing sraIM.cmd runs in a loop (4911641)

The gateway instance is created and the Select the SRA proxy type you want to manage is displayed again.

Workaround    

Select the Cancel button to exit.

Gateway is not using the JDK specified during the Identity Server SDK install (4906652)

Identity Server install fails if the web container base directory contains spaces (4977970)

The tag swapping does not support directory name that contains space.

Workaround    

Do not specify spaces in directory paths.

nlp multi-instance script is missing (5039699)

The nlpmultiinstance script is missing in the portal-install-dir\bin directory. So you can not create Netlet proxy instance.

rwpmultiinstance is not in batch file format (5039702)

The rwpmultiinstance script is in unix format in portal-install-dir\bin directory. So, you can not create a Rewriter proxy instance.

certadmin script is missing on Portal Server node(5041819)

You can not create, delete, modify certificate from certificate database for rewriter and netlet proxy.

Online help is not available for Secure remote access admin console (4913957)

Workaround    

Copy the five files attrib2.html, attrib3.html, attrib4.html, attrib5.html, srahelp.html from the directory identity-server-install-dir\public_html\online_help\docs_en_US\ps to the directory app-server-install-dir\domains\domain1\server1\docroot\online_help\docs_en_US\ps.

Appserver install on Windows 2003 says unsupported OS (5043804)

Workaround    

Just continue with the installation and the software will install properly.

Install fails if the directory name contains spaces (4908636)

Workaround    

Do not specify spaces in directory paths during installation.

Certain channels do not display the Help (4977957)

PortalServer uninstall fails to clean registry entries (5003802)

Rewriter proxy is not working through Gateway (5041859)

Netlet proxy is not working (5041888)

---

How to Report Problems and Provide Feedback

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

Sun Software Support services online at
http://www.sun.com/service/sunone/software

This site has links to the Knowledge Base, Online Support Center, and ProductTracker, as well as to maintenance programs and support contact numbers.

The telephone dispatch number associated with your maintenance contract

So 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

You might also find it useful to subscribe to the following interest groups, where Sun Java System Portal Server topics are discussed:

snews://

snews://

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Email your comments to Sun at this address:

docfeedback@sun.com

Please include the part number and the full title of the document that you would like to address in the subject line of your email. The part number can be found on the title page of the book, and is usually a seven or ten digit number, for example: 123-4567-10.

---

Additional Sun Resources

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

Documentation for <Associated_Project>
http://docs.sun.com/coll/<Proj_Collection>
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://www.sun.com/supportraining
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 © 2003 Sun Microsystems, Inc. All rights reserved.

Sun, Sun Microsystems, the Sun logo, Solaris, Java and the Java Coffee Cup logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Use of Portal Server is subject to the terms described in the license agreement accompanying it.