Chapter 3   Configuration Files

Process Manager 6.0 uses several configuration files to define installation values, server configurations, clusters and application versions.

Much of what they do is behind the scenes, but you may need to know about them from time to time. This chapter describes what you need to understand about each and how you might need to modify them.

This chapter describes these topics:

• Overview



• Process Manager Files and Folders



• Error Messages and Logs

Overview

---

Configuration files are included in the components that you install as part of Process Manager. The configuration files that are important for Process Manager administrators touch on several areas:

• The iPlanet Web Server Files



• The Process Builder Preferences File

The iPlanet Web Server Files

The IPlanet Web Server has several configuration files, but the single one that is relevant to Process Manager is the web server object configuration file (obj.conf).

The iPlanet Web Server obj.conf file is used to do some name translation. The following lines are added to your obj.conf file as part of the Process Manager installation:

NameTrans fn="pfx2dir" from="/Administrator.apm" dir="d:/software/iPlanet/iAS6/bpm/html/Administrator.apm/en"
NameTrans fn="pfx2dir" from="/Business.apm" dir="d:/software/iPlanet/iAS6/bpm/html/Business.apm/en"
NameTrans fn="pfx2dir" from="/Express.npm" dir="d:/software/iPlanet/iAS6/bpm/html/Express.npm/en"
NameTrans fn="pfx2dir" from="/PMResources" dir="d:/software/iPlanet/iAS6/bpm/resources"
NameTrans fn="pfx2dir" from="/BPM" dir="d:/software/iPlanet/iAS6/bpm/applications"

The Process Builder Preferences File

The Process Builder has a preferences.ini file that identifies which cluster and corporate directory to use when designing applications.

You can add multiple cluster and directory entries to offer a choice to designers as they build applications in Process Builder. Each application can only belong to one cluster at a time and have access to a single user directory at a time, but a designer may work with several clusters at a time.

The preferences.ini file provides the unique cluster DN and identifies which corporate user directory is included in the cluster. If you cut and paste the two lines that result from a successful cluster creation, you are providing the preferences.ini file with one cluster and one corporate user directory. See "Creating a Cluster and Getting Started" in the Installation Guide for information about this hand-off to Process Builder. See Directory Server Terms and Attributesfor details about how to structure LDAP information.

---

Note	If the process designer and the administrator are not the same individual, the administrator must give the following URLs to the process designer for inclusion in the preferences.ini file.

---

• To add a cluster entry, use this LDAP URL format:


   cluster=ldap://Bind DN:Password@yourConfigDirServer:port/clusterDN

• To add an entry for a corporate user Directory, use this LDAP URL format:


   corp_dir=ldap://corporateDirectoryServer:port/corpDirectoryBaseDN

Process Manager Files and Folders

---

The Process Manager installer adds many files and folders to your local system as it installs the Process Manager components.

The Process Manager files are added to serverRoot/bpm.

Process Builder files and folders are added to the serverRoot/builder folder.

Error Messages and Logs

---

There are several logs in Process Manager: some are for Process Administrator errors or information, others are specific to an application. You can directly open an application's logs or the Process Manager logs in your web browser window.

• Process Builder logs are located at: serverRoot/builder/support/log/error.html and warning.html.



• Process Administrator logs are located in the serverRoot/bpm/admin/logs folder. They are info.html, error.html, and security.html.



• Process Manager applications use several log files, with each application server in a cluster having its own set of log files. Process Manager administrators can view these application logs that are maintained for each application on a per-server basis:



• information log (info.html): shows information about the application's operations.



• error log (error.html): shows the errors that have occurred with the application.



• security log (security.html): shows the security violations that have occurred with the application.




The application log files are located at serverRoot/bpm/applications/applicationName/logs.

There are other log files for each of the other servers:

• web server: serverRoot/https-yourWebServer/logs



• Administration Server: serverRoot/admin-serv/logs



• Directory Server: serverRoot/slapd-yourDirServer/logs