iPlanet Process Manager, Version 6.5 Release Notes |
These release notes contain important information available at the time of the release of iPlanet Process Manager, Version 6.5. New features and enhancements, known problems, and other information are addressed here. Read this document before you begin using iPlanet Process Manager.
An electronic version of these Release Notes can be found at the Sun documentation website: http://docs.sun.com. Check the website after installing your software and periodically thereafter to view the most up-to-date release notes and manuals.
These release notes contain the following sections:
Product Certification of iPlanet Process Manager 6.5 on iAS EE 6.5 SP1
Supported Systems and Software
What's New in iPlanet Process Manager, Version 6.5
Bugs Fixed in Process Manager, Version 6.5
This document has changed since the initial iPlanet Application Server Enterprise Edition 6.5 release.
Table 1 shows the revision history for this document, and lists the affected sections.
Release Date |
Affected Sections |
---|---|
August, 2002 |
Original release of this document |
November 27, 2002 |
Following sections added to document: |
iPlanet Process Manager 6.5 has been certified to run on iPlanet Application Server, Enterprise Edition, 6.5 SP1.
For information about upgrading your Application Server, refer to the iPlanet Application Server, Enterprise Edition, 6.5 SP1 Release Notes.
iPlanet Process Manager, Version 6.5 is a product bundled with the iPlanet Application Server Enterprise Pro Edition 6.5. The other products bundled with the Application Server are:
iPlanet Web Server Enterprise Edition 6.0 SP2
iPlanet Application Server Enterprise Edition 6.5
Unified Integration Framework 6.5
It is important to follow the installation instructions for each component of iPlanet Application Server carefully. Read the release notes for each individual product prior to installation.
The following operating systems and software are supported with this release of Process Manager. If you are running non-supported versions of these products, you must upgrade to a supported version.
Product Type |
Supported Versions |
---|---|
Operating Systems |
Solaris 2.6, 2.8 Windows NT, SP6A Windows 2000 Advanced Edition Windows 2000 Server Edition, SP2 Windows 2000 Professional Edition |
Web Servers |
iPlanet Web Server, Enterprise Edition 4.1, SP 7 iPlanet Web Server, Enterprise Edition 6.0, SP1 iPlanet Web Server, Enterprise Edition 6.0, SP2B |
Directory Servers |
iPlanet Directory Server 5.0, SP1 iPlanet Directory Server 5.1 |
Application Server |
iPlanet Application Server, 6.5, Maintenance Update 2 (iAS MU2)1 iPlanet Application Server, 6.5, SP1 |
Database Servers and Clients |
Oracle 8.1.6, 8.1.7, 9i Servers, Oracle 8.1.7, 9i Clients Sybase 11.9.2, 12 Servers, Sybase Open/Client System 12 Informix 9.2 Server, Informix SDK 2.7 UC3 Client |
Third-party JDBC Drivers |
Oracle 8.1.7: Type 2 and Type 4 Sybase jConnect for JDBC 5.2 Type 4 Informix JDBC v2.1 Type 4 |
JDK |
JDK 1.3.1_042 |
Web Browsers |
Netscape 4.7x Microsoft Internet Explorer 5.x, 6.0 |
1 The iPlanet Application Server 6.5, Maintenance Update 2 is shipped only to customers who have purchased iPlanet Application Server, Enterprise Pro Edition, 6.5. For more information about this Maintenance Update patch, see the section "Required Patches". 2 For more information about this JDK, see the section "Required Patches." |
This release contains two patches required for stable operation of Process Manager applications:
JDK 1.3.1_04
The JDK is only available for the Solaris platform.
iPlanet Application Server, Maintenance Update 2 (iAS MU2)
The Maintenance Update is available for Solaris and Windows platforms.
The patches are located in the patches directory on the iAS EPE CD or in the download.
Install iPM and iAS using the unified installation located in the nt or solaris directories.
Install the patches according to your platform as described below.
Install the patches according to your platform as described below.
Install Process Manager components by running the setup program located in the nt or solaris directories.
When the setup program starts, select only Process Manager components.
Go to <install-dir>/ias/usr and change the name of the java directory to java_bak.
Unzip SolarisJDK.zip to <install-dir>/ias/usr.
Untar the compressed MU2 patch to a temporary location.
Follow the readme instructions to install the MU2 patch on top of iAS.
Unzip the compressed MU2 patch to a temporary location.
Follow the readme instructions to install the MU2 patch on top of iAS.
The following enhancements are new to this release of iPlanet Process Manager:
"Secure Application Deployment"
"Application Deployment Through a Proxy"
These release notes cover enhancements specific to iPlanet Process Manager 6.5. For enhancements to the other products bundled with iPlanet Application Server Enterprise Pro Edition 6.5, read the release notes for each individual product.
Process Manager, Version 6.0, SP3 introduced support for application deployment to a secure Web Server from the Process Manager Builder client. In that release, you had to configure Builder's security environment by hand.
The Process Manager 6.5 release automatically configures Builder for secure application deployment. For a detailed description of this new functionality, see "Configuring Builder for Secure Deployment" in the Process Builder's Guide.
You must configure your Web Server for secure deployment to take advantage of this feature. For information about securing your Web Server, see "Securing Your Web Server" in the Web Server Administrator's Guide.
Process Manager supports deployment of applications through a proxy server using both normal (http) and secure (https) protocols. For more information, see "Configuring Builder for Deployment Through a Proxy" in the Process Builder's Guide.
Process Manager 6.5 provides web services support using the Apache implementation of the Simple Object Access Protocol (SOAP) specification. SOAP is an XML-based protocol for the exchange of information in a decentralized, distributed environment.
To learn how to use SOAP to call a Process Manager application, read Chapter 7, "Web Services" in the Process Manager Programmer's Guide.
iPM 6.5 was tested using the Apache SOAP 2.2 implementation. For information on how to install Apache SOAP 2.2, visit the following location: http://developer.iplanet.com/appserver/samples/soap/docs/soap-install.html
You are required to apply a patch (ipmsoap-2_2.jar) to the Apache SOAP 2.2 installation for the web services feature to work successfully. This patch allows the Apache SOAP service to work with WSDL clients and with EJBs in the iPlanet Application Server. For more information, read Chapter 7, "Web Services" in the Process Manager Programmer's Guide.
Process Manager ships with a sample Apache SOAP client application that instantiates the Credit History application, allowing the user to complete the Check Authorization activity.
Note |
The SAOPProperties.conf and CALLParameters.conf files required for the sample application should be placed in the classpath. |
Process Manager 6.5 introduces support for multiple iPM clusters on a single iPlanet Application Server instance. Changes to the directory structure of the default cluster, LDAP Schema, and authentication enabled this support. Because of these changes, there is no upgrade path for iPM 6.0 SPx to iPM 6.5.
As a Process Manager Administrator you can set up either single or multiple clusters, as described below:
single cluster
Choose this option if you use only one type of database to collect and manage Process Manager process application data, and one configuration or corporate directory.
The single cluster implementation is now supported, but will be phased out in a future release.
multiple clusters
Choose this option if you use more than one type of database to collect and manage Process Manager process application data, or use different configuration or corporate directories.
A multiple cluster implementation allows you to configure a separate cluster to accommodate each department's database, configuration directory, and corporate directory requirements. For example, your marketing department uses Sybase to manage its process application data, while your sales department requires the use of an Oracle database. They also use different configuration directories to store application definitions.
In many cases, you use the multiple cluster implementation to create only a single cluster. This implementation allows you the ability to create another cluster at a later time.
If you are new to Process Manager, Sun recommends that you use the multiple cluster implementation described in the Process Administrator's and Business Manager's Guide.
If you developed and deployed applications using iPM 6.0 SPx, you may want to create a cluster using the single cluster implementation described in the Process Administrator's and Business Manager's Guide. After you successfully deploy your applications to iPM 6.5, you should follow the steps in the section "Migration of iPM 6.0 Application Data to iPM 6.5" to deploy those applications to a multiple cluster implementation.
Windows 2000 Professional and Windows 2000 Server SP2 platforms are now supported in production and development environments.
Below is a short description of the most important bugs fixed in Process Manager, Version 6.5.
This section contains a listing of the more important bugs known at the time of the Process Manager, Version 6.5 release. For known problems related to specific bundled products, please read the release notes for each product.
iPlanet Process Manager does not allow migration of Process Manager applications from 6.0 to 6.5. You must uninstall iPM 6.0, install iPM 6.5, and migrate the application data inside the database instance. This is done by creating a dummy database instance in the 6.5 version of iPM, redeploying all 6.0 applications to 6.5, and then changing the reference pointer from the 6.5 database instance to the 6.0 database instance.
Enhancements were made to the Process Engine and the user interface in this release of Process Manager to allow for the creation of multiple Process Manager clusters on a single iPlanet Application Server instance. New interfaces have been introduced in Process Manager to support this feature. These include interfaces for administrators and end-users. Old interfaces will continue to work and be supported. Sun strongly recommends a migration to new interfaces because old interfaces will be phased out in future releases.
Enabling multiple iPM cluster support included changes to the directory structure of the default cluster, LDAP Schema, and authentication. Because of these changes, you must recreate your cluster on iPM 6.5. There are three migration strategies you can take to migrate application data from 6.0 SPx to 6.5.
If you select this path, use the old interfaces from 6.0 SPx in 6.5 to create a cluster and manage your applications. There are no changes to the old interfaces:
http://serverName/Administrator.apm
http://serverName/Express.npm
http://serverName/Business.apm
In this scenario the authentication is managed by the container as before.
This is the recommended path because default (single) cluster support will be phased out in a future release.
If you select this path, use the new interfaces to create a cluster and manage your applications:
http://serverName/SiteAdmin.apm
http://serverName/ClusterAdmin.apm
http://serverName/ProcessExpress.npm
http://serverName/ProcessBusiness.apm
In this scenario, create a cluster based on a unique cluster name you supply. During cluster creation, a corresponding bean is registered with iAS. The process engine manages authentication instead of the Application Server.
During cluster creation, you must provide a comma-separated list of LDAP users. These users function as administrators of the cluster. Only these administrative users have authorization to deploy applications to the cluster.
If you select this path, use the old interfaces while migrating from a default cluster in 6.0 SPx to a default cluster in 6.5. Then deploy applications normally onto the default (single) cluster on 6.5. When you are ready to move to a multiple cluster implementation, use the new interfaces to create the named (multiple) cluster. You must save any applications deployed to the default cluster in 6.5 under a different name before you deploy them to a named cluster.
The naming conventions for servlet and bean registration during application deployment have changed for this release. As a result, you must redeploy iPM 6.0 SPx applications to an iPM 6.5 cluster.
There were no changes made to Process Builder for the iPM 6.5 release. You could always use Process Builder to deploy to multiple clusters and this support is sufficient to meet the needs of the new features in iPM 6.5.
When you import an application into iPM 6.5, it will point to the corporate directory you used with iPM 6.0 SPx. You must change the reference to point to the iPM 6.5 cluster's new corporate directory. You must also assign user groups from the new corporate directory to the application.
The database schema has not changed in iPM 6.5. You can migrate application data from iPM 6.0 SPx to iPM 6.5.
The following steps describe how to migrate application data from iPM 6.0 SPx to iPM 6.5:
Create a cluster in iPM 6.5 using either the old http://serverName/Administrator.apm or the new http://serverName/SiteAdmin.apm interface.
For this example, the name of this cluster is iPM65Cluster (cn=iPM65Cluster,o=NetscapeRoot).
Use a dummy database with the datasource name iPM65DS (this datasource points to the dummy database).
Register a datasource in iPM 6.5 pointing to database A.
Call this datasource iPM6xto65DS.
Import a 6.0 SPx application in iPM 6.5 using Process Builder.
Change the corporate directory and assign users to groups.
Deploy the application to the cluster iPM65Cluster.
Start iAS Console and navigate to the Directory Server.
Under NetscapeRoot you should see a node whose name is the cluster name. In this case the cluster name is iPM65Cluster.
Right click on the iPM65Cluster node.
The properties window for iPM65Cluster appears.
Edit the datasource name in the cluster properties. (cn=iPM65Cluster,o=NetscapeRoot)
Change the name from iPM65DS to iPM6xto65DS.
Additionally, if the database user name is different than the one used in the original (6.0 SPx) cluster, change the database user name field in the cluster properties dialog and the application properties dialog.
Restart the Application Server.
Application data from iPM 6.0 SPx is now available to the cluster created on iPM 6.5.
If you have problems with Process Manager, contact iPlanet customer support using one of the following mechanisms:
iPlanet online support web site at http://www.sun.com/service/support/software/iplanet/index.html
From this location, the CaseTracker and CaseView tools are available for logging problems.
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
Useful information can be found at the following Internet locations:
Sun ONE Documentation
Sun ONE Software Products and Service
Sun ONE Support and Knowledge Base
Sun ONE Consulting and Professional Services
Sun ONE Developer Information
Sun ONE Software Training