Configuring the Process Federation Server database (deprecated)

Edit online

Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15

The Process Federation Server database stores federated saved search definitions that Process Portal uses.

Before you begin

The Process Federation Server database must exist. For more information, see Creating the Process Federation Server database (deprecated).

Attention: 25.0.1.0

Storing saved search definitions that are used by Process Portal in a relational database is deprecated with this version. To help ensure compatibility and future support, use the Federated Data Repository index as the data store for the Process Federation Server.

For more information on how to configure the Process Federation Server data store, see Configuring properties for the data store.

To migrate existing saved search definitions, see Migrating saved search definitions to a Federated Data Repository index.

About this task

Federated environments typically have one database instance for each federated system and a separate instance for Process Federation Server. The server.xml file on Process Federation Server contains the configuration properties for the federated systems and for the Process Federation Server database.

To configure the Process Federation Server database, you must specify values for the <library> and the <dataSource> elements in the server.xml file. Process Federation Server uses this information to connect to the database. If the Process Federation Server database uses the same database management system as the business process management systems, the databases can use the same library specification. In addition, you must specify the database properties in the ibmPfs_federatedPersistence element.

Procedure

Open the server.xml configuration file for editing.
By default, the configuration file is in the pfs_install_root/usr/servers/server_name directory on Process Federation Server.
Ensure that the server.xml file contains a configured library element for the database management system that you are using for the Process Federation Server database.
Uncomment the appropriate library element if it is commented out.
The following code snippet shows an example of a configured library element for an IBM® Db2® database:
```
<library id="DB2JCC4Lib">
   <fileset dir="pfs_install_root/wlp-ext/jdbcdrivers/DB2" 
      includes="db2jcc4.jar db2jcc_license_cisuz.jar db2jcc_license_cu.jar"/>
</library>
```
Configure the dataSource element for your Process Federation Server database.
Note: Configure a datasource element with a different id for each federated system.
Uncomment the appropriate dataSource element if it is commented out, and specify values for the databaseName, user, and password properties.
The following code snippet shows an example of a configured dataSource element for a Db2 database:
```
<dataSource id="pfs_db2" 
   commitOrRollbackOnCleanup="commit" isolationLevel="TRANSACTION_READ_COMMITTED" 
   jndiName="jdbc/pfsdata" type="javax.sql.DataSource"> 
   <jdbcDriver libraryRef="DB2JCC4Lib"/> 
   <properties.db2.jcc serverName="localhost" portNumber="50000" 
      databaseName="PFSDB" user="db2admin" password="db2admin" /> 
</dataSource>
```
Specify the schema name and the data source ID for the Process Federation Server database instance in the ibmPfs_federatedPersistence element:
```
<ibmPfs_federatedPersistence 
  schemaName="FEDERATED"
	  dataSourceRef="pfs_db2"/>
```
schemaName

Not required. The name of the schema that contains the database tables. It must be the same as the name that was used when the Process Federation Server tables were created. The default value is FEDERATED.

dataSourceRef

Required. The data source ID for the Process Federation Server database instance. This property refers to the data source ID that you set in step 3.

Results

After the Process Federation Server database is configured, you can save searches in Process Portal.