Contents
|
| iPlanet Process Manager, Version 6.5 Installation Guide |
Chapter 4 Post-installation Tasks and Uninstalling Process Manager
This chapter discusses what happens during installation, gives troubleshooting hints for installation, discusses how to create a cluster after completing the installation procedure, and describes how to uninstall Process Manager.
- "What Happens During Installation"
- "Configuring After a Webless Installation"
- "Setting up Database Connectivity"
- "Creating a Cluster"
- "Accessing Process Manager Components"
- "Uninstalling Process Manager"
What Happens During Installation
When you install Process Manager, the installer makes several modifications to files on your machine.
The Installer performs the following actions in order:
- Beans and servlets are registered: The installer registers eight servlets and three beans with the configuration directory.
Servlets:
ProcessExpress.npm
Beans:
- iPlanet Web Server files are updated:
obj.conf: The installer modifies this file to allow name translations for Process Manager URLs.
- bpm.ldif file is modified. Generic parameters are replaced by installation-specific data.
This file, stored in the serverRoot/bpm/admin directory, contains the LDIF entries that are added to the configuration directory for iPlanet Console integration.
- Installation log files are created.
Installation log files for Windows are stored in the following directory:
serverRoot\bpm\bpm_install.log
Installation log files for Solaris are stored in the following places:
pre-installation log files
$PM_HOME/BPM/installfiles/pae_preinstall_UserID.log
where userID is the user ID that is running the installation script and $PM_HOME is where Process Manager has been installed.
post-installation log files
$PM_HOME/BPM/installfiles/pae_postinstall_UserID.log
log files for registration of servlets and beans
$PM_HOME/BPM/installfiles/pae_app_reg.log
Configuring After a Webless Installation
For production purposes, you may elect to install the Process Manager and the Application Server on a separate machine from the Web Server. Once you complete the webless installation you must:
- Make sure the Web Connector plug-in is installed on the machine containing the Web Server.
For details on installing the Web Connector plug-in on the Web Server machine, see the iPlanet Application Server Installation Guide.
- Copy directory files from the machine where you installed the Process Manager to the Web Server machine.
- Update the Web Server's obj.conf file.
To copy the directory files
- Create a directory named iPlanet/iPM65/bpm on the machine where the Web Server is installed.
- Assuming you installed Process Manager in an iPlanet/iPM65 directory, copy the following directories from the iPlanet/iPM65/bpm directory on the machine where you installed Process Manager to the Web Server machine directory you just created.
To update the obj.conf file
- On the machine where the Web Server is installed, open the obj.conf file.
The obj.conf file is located in the following directory:
webserverlocation\https-instance name\config
- Insert the following lines under the <object name=default> section:
NameTrans fn="pfx2dir" from="/SiteAdmin.apm" dir="D:/iplanet/ipm65/bpm/html/SiteAdmin.apm/en"
NameTrans fn="pfx2dir" from="/ClusterAdmin.apm" dir="D:/iplanet/ipm65/bpm/html/ClusterAdmin.apm/en"
NameTrans fn="pfx2dir" from="/ProcessBusiness.apm" dir="D:/iplanet/ipm65/bpm/html/ProcessBusiness.apm/en"
NameTrans fn="pfx2dir" from="/ProcessExpress.npm" dir="D:/iplanet/ipm65/bpm/html/ProcessExpress.npm/en"
NameTrans fn="pfx2dir" from="/Administrator.apm" dir="D:/iPlanet/iPM65/bpm/html/Administrator.apm/en"
NameTrans fn="pfx2dir" from="/Business.apm" dir="D:/iPlanet/iPM65/bpm/html/Business.apm/en"
NameTrans fn="pfx2dir" from="/Express.npm" dir="D:/iPlanet/iPM65/bpm/html/Express.npm/en"
NameTrans fn="pfx2dir" from="/PMResources" dir="D:/iPlanet/iPM65/bpm/resources"
NameTrans fn="pfx2dir" from="/BPM" dir="D:/iPlanet/iPM65/bpm"
Note
- Add the following line to your obj.conf file if it does not already exist:
Service method=(GET|HEAD|POST) type=*~magnus-internal/* fn=send-file
Restart the Web Server to register the new obj.conf settings.
Setting up Database Connectivity
After installing Process Manager 6.5, you must establish database connectivity:
- Windows Platforms
You are required to set up database connectivity for third-party JDBC drivers on Windows. If you use native database drivers, you do not need to set up database connectivity for Windows. You establish database connectivity for third-party JDBC drivers using the jdbcsetup utility, located in the <ipm_install_directory>/ias/bin directory. For more information on the jdbcsetup utility, see the iPlanet Application Server Administrator's Guide.
- Solaris Platforms
You are required to set up database connectivity if you use native or third-party JDBC database drivers on Solaris before you create a cluster. You do this using the db-setup utility, located in the <ipm_install_directory>\ias\bin directory. For more information on the db-setup utility, see the iPlanet Application Server Administrator's Guide.
Note After you establish database connectivity, restart your iPlanet Application Server for your new settings to take effect.
For information on configuring specific third-party JDBC drivers with iAS, see iPlanet Knowledge Base article number 7831, entitled "Registering Third-party JDBC Drivers with iAS for Database Connectivity with iPM Applications.'
Creating a Cluster
After installing all components and establishing database connectivity, you must create an iPlanet Process Manager cluster. This cluster associates the following components with each other:
- an LDAP-compliant corporate user directory
- an LDAP-compliant configuration directory
- a relational database
After you create an iPlanet Process Manager cluster, you can deploy applications you create with Process Manager Builder to that cluster. For more information about creating a cluster, see the Process Administrator's and Business Manager's Guide.
Accessing Process Manager Components
This section describes how to launch or access each of the Process Manager components after installation.
- "Launching Process Builder"
- "Accessing Process Express"
- "Accessing Process Administrator"
- "Accessing Process Business Manager"
Launching Process Builder
Process Builder is a Java application that enables you to build Process Manager applications. When a Process Manager cluster has been created and you have modified the file preferences.ini to point to a cluster, you can deploy applications from the Builder to the Process Manager Engine.
To launch Process Builder on Windows systems, execute this file:
<builder_install_directory>\Builder.exe
To launch Process Builder on Solaris systems, go to the installed Builder directory and call the following command:
./Builder.sh &
For details on using Process Builder, see the Process Builder's Guide.
Accessing Process Express
Process Express is a web-based interface where users can view their worklists and can start new processes.
The URL Process Manager application users access to launch Process Express depends on the cluster implementation the Process Manager administrator uses.
- single cluster
http://ProcessManager_server:port_number/Express.npm/
- multiple cluster:
http://ProcessManager_server:port_number/ProcessExpress.npm/
The Process Express client requires the user to log in, and then displays the worklist appropriate to that user.
For more information about Process Express, see the Process Express User's Guide.
For information on the difference between single and multiple cluster implementations, see the Process Administrator's and Business Manager's Guide.
Accessing Process Administrator
After you have installed Process Manager Engine and created a cluster, you can access the Process Administrator interface to administer Process Manager clusters and applications deployed to those clusters.
The URL Process Manager administrators access to launch Process Administrator depends on the cluster implementation the Process Manager administrator uses:
- single cluster
http://ProcessManager_server:port_number/Administrator.apm/
- multiple cluster
http://ProcessManager_server:port_number/ClusterAdmin.apm
For more information about Process Administrator and the difference between single and multiple cluster implementations, see the Process Administrator's and Business Manager's Guide.
Accessing Process Business Manager
After a Process Manager application has been deployed to a cluster, you can perform administrative operations on process instances in an application by using the Business Manager interface.
The URL Process Manager administrators and business managers access to launch Process Business Manager depends on the cluster implementation the Process Manager administrator uses:
- single cluster
http://ProcessManager_server:port_number/Business.apm/
- multiple cluster
http://ProcessManager_server:port_number/ProcessBusiness.apm/
For more information about Process Business Manager and the difference between single and multiple cluster implementations, see the Process Administrator's and Business Manager's Guide.
Uninstalling Process Manager
If you currently have a previous version of Process Manager installed on your Windows or Solaris machine, you must migrate your application data to the current version. For information about migration issues and application data migration, see the Process Manager Release Notes.
- "Uninstalling Process Builder Only"
- "Uninstalling Process Manager"
Uninstalling Process Builder Only
If you installed Process Builder as a stand-alone application on your machine, you can uninstall the application by performing the following steps.
To uninstall Builder on Windows
- Delete the Process Builder menu item from your Start Menu.
- In your file system, delete the \builder directory.
To uninstall Builder on Solaris
- In your file system, delete the /builder directory.
Uninstalling Process Manager
You can uninstall any of the following products using the Process Manager uninstall program:
- iPlanet Directory Server
- iPlanet Application Server
- iPlanet Process Manager
To Uninstall Process Manager on Windows
- Select Programs > iPlanet Application Server 6.5 > Uninstaller from the Start menu.
- Select the items you want to uninstall.
- Select Uninstall and provide the administrator username and password.
- Delete the builder directory from the Process Manager directory when the uninstall is complete.
See the individual Installation Guides and Release Notes for any other post-uninstallation tasks you must perform for the Application Server and the Directory Server.
To Uninstall Process Manager on Solaris
- Run the uninstall command in the iPlanet Process Manager directory.
- Select the items you want to uninstall when prompted.
- Select Uninstall and provide the administrator username and password.
- Delete the builder directory from the Process Manager directory when the uninstall is complete.
See the individual Installation Guides and Release Notes for any other post-uninstallation tasks you must perform for the Application Server and the Directory Server.
Contents