Monday, 30 March 2015

IBM Operational Decision Manager V8.7.0.1 Fix Pack


This came via my IBM colleague, Dan Selman, through the medium of Twitter: -


This cumulative fix pack updates WebSphere Operational Decision Management V8.7.0 to V8.7.0.1.


IBM provides periodic fixes for the Operational Decision Manager family (formerly known as WebSphere Operational Decision Management). The following is a complete list of fixes for the components IBM Decision Server and IBM Decision Center.

IBM Installation Manager - Using response file variables

I needed this: -


so here it is :-)

This is also quite useful: -


IBM Operational Decision Manager - Performance Improvements

This popped up in my Twitter feed earlier: -

Improve performance for IBM Operational Decision Manager, Part 1: Reduce rule execution time

IBM® Operational Decision Manager (ODM) offers a variety of options for optimal performance. Each organization's environment and needs are unique, so guidance about settings to increase performance and to streamline resource             management is essential. This tutorial provides a brief overview of the different IBM ODM modules, and how they interact with each other, and recommended settings for performance improvements that have been found to have the most impact on rule execution. This content is part of the IBM Business Process Management Journal.

I am guessing that there will be more coming from this author, on this precise topic, so please follow the article linked for the rest of the series .....

Thursday, 26 March 2015

CWTDS0021E: The user registry configuration was changed in a way that causes the access to the IBM BPM document store to fail for the technical user 'deAdmin'.

For other reasons, relating to incorrectly formatted SSL certificates within a WAS profile, I needed to recreate my IBM BPM 8.5.5 environment yesterday.

I did this by deleting the WAS profiles, which took care of the Deployment Environment, and had my DB2 SME drop the nine Messaging Engine tables from the Common/Shared DB ( CMNDB ).

I recreated the Deployment Environment using BPConfig, and all seemed well .....

Until a colleague tried to invoke a multi-stage BPD, which triggers events to be consumed by IBM Business Monitor.

Guess what ?

Yes, my Deployment Environment rebuild hadn't quite worked as purely as I thought.

In the WAS logs, we saw: -

com.ibm.bpm.embeddedecm.exception.UserRegistryConfigurationProblemException: com.ibm.bpm.embeddedecm.exception.UserRegistryConfigurationProblemException: CWTDS0021E: The user registry configuration was changed in a way that causes the access to the IBM BPM document store to fail for the technical user 'deAdmin'.

Explanation: The technical user defined in the BPM role type 'EmbeddedECMTechnicalUser' is not permitted to access the 'BPM' domain.

Action: Revert the recent user registry configuration changes and follow the instructions of the 'Administering the technical user for the IBM BPM document store' topic in the IBM BPM Information Center to ensure the technical user keeps access to the IBM BPM document store.


As per the message, I referenced: -


which made reference to a series of useful Jython commands, including: -

AdminTask.maintainDocumentStoreAuthorization('[-deName PSCell1De1 -list]')

 AdminTask.maintainDocumentStoreAuthorization('[-deName PSCell1De1 -add uid=deAdmin,o=defaultWIMFileBasedRealm]')

 AdminTask.maintainDocumentStoreAuthorization('[-deName PSCell1De1 -add #AUTHENTICATED-USERS]')

 all of which failed with: -

WASX7015E: Exception running command: "AdminTask.maintainDocumentStoreAuthorization('[-deName PSCell1De1 -list]')"; exception information:

com.ibm.bpm.embeddedecm.exception.UserRegistryConfigurationProblemException: com.ibm.bpm.embeddedecm.exception.UserRegistryConfigurationProblemException: CWTDS0021E: The user registry configuration was changed in a way that causes the access to the IBM BPM document store to fail for the technical user 'deAdmin'.

Explanation: The technical user defined in the BPM role type 'EmbeddedECMTechnicalUser' is not permitted to access the 'BPM' domain.

Action: Revert the recent user registry configuration changes and follow the instructions of the 'Administering the technical user for the IBM BPM document store' topic in the IBM BPM Information Center to ensure the technical user keeps access to the IBM BPM document store.

At that point, I started to wonder if I should've had John clear down ALL of the DBs.

So I completely shut down the Deployment Environment and had him do just that. He had a nice scripted process to recreate them, so they were back in the game within ~10 minutes.

I then needed to bootstrap the AppCluster DB tables: -

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/bootstrapProcessServerData.sh -clusterName AppCluster

and then start the Deployment Environment.

This time, the clever ECM Jython command worked: -

AdminTask.maintainDocumentStoreAuthorization('[-deName PSCell1De1 -list]')

returning: -

"Authorization on the domain for the IBM BPM document store\nCWTDS2034I: Access is granted to the IBM BPM document store domain 'uid=deAdmin,o=defaultWIMFileBasedRealm' with access mask '459,267'.\nAuthorization on the object store for the IBM BPM document store\nCWTDS2035I: Access is granted to the IBM BPM document store object store 'uid=deAdmin,o=defaultWIMFileBasedRealm' with access mask '838,205,440'."

 which is nice.

IBM HTTP Server and the Global Security Toolkit - Not quite Harry Potter

I have blogged about this before: -


but I finally have a much clearer idea of the problem, and the pukka solution.

When creating a self-signed  SSL certificate in IHS, via a command such as: -

/opt/IBM/HTTPServer/bin/gskcapicmd -cert -create -db /opt/IBM/HTTPServer/ssl/keystore.kdb -pw passw0rd -size 2048 -dn "cn=hostname.domain.co.uk,dc=uk,dc=ibm,c=com" -label "hostname.domain.co.uk" -default_cert yes

I'd end up with an exception: -

CTGSK3024W Invalid value for parameter "-dn" (cn=hostname.domain.co.uk,o=domain,o=co,c=uk).

Initially, I thought that the problem was with the format of the Distinguished Name, so I used an escape character in front of each comma: -

/opt/IBM/HTTPServer/bin/gskcapicmd -cert -create -db /opt/IBM/HTTPServer/ssl/keystore.kdb -pw passw0rd -size 2048 -dn "cn=hostname.domain.co.uk\,dc=uk\,dc=ibm\,c=com" -label "hostname.domain.co.uk" -default_cert yes

which worked OK .... or so I thought.

However, when I looked at the certificate in Firefox, I noted that the Issuer contained an invalid Common Name (CN) - it actually held the DN: -


I spent a wee while digging around, and found that, if I instead used ikeycmd : -

/opt/IBM/HTTPServer/java/jre/bin/ikeycmd -cert -create -db /opt/IBM/HTTPServer/ssl/keystore.kdb -pw passw0rd -size 2048 -dn "cn=hostname.domain.co.uk,o=domain,o=co,c=uk" -label "hostname.domain.co.uk" -default_cert yes


the certificate created with the correct Issuer.

Which is unusual.

I've experimented further, including: -

/opt/IBM/HTTPServer/bin/gskcapicmd -cert -create -db /opt/IBM/HTTPServer/ssl/keystore.kdb -pw passw0rd -size 2048 -dn "cn=hostname.domain.co.uk,dc=domain,dc=co,dc=uk" -label "hostname.domain.co.uk" -default_cert yes

In other words, I continued to experiment with the format of the DN.

According to this document: -


the crucial thing is to ensure that the DN is formatted to a certain X.500 standard: -

-dn <dist_name>

The X.500 distinguished name that uniquely identifies the certificate. The input must be a quoted string of the following format (only CN is required):

        CN=common name
        O=organization
        OU=organization unit
        L=location

        ST=state, province
        C=country
        DC=domain component
        EMAIL=email address

For Example: "CN=weblinux.Raleigh.ibm.com,O=ibm,OU=IBM HTTP Server,L=RTP,ST=NC,C=US"

Multiple OU values are now supported. Simply add additional OU key\value pairs to the specified distinguished name. If the OU value requires a comma (',') then you must escape it with '\\'

For Example: "CN=weblinux.Raleigh.ibm.com,O=ibm,OU=IBM HTTP Server,OU=GSKit\\, Gold Coast,L=RTP,ST=NC,C=US"

Therefore, via trial and error, I've found a syntax that works for my client, and also works with GSK rather than depending upon ikeycmd, as hosting a JRE on a web server is typically a bad idea.

For evidence, please see the 39 Steps here: -



Wednesday, 25 March 2015

Sunday, 22 March 2015

Getting to grips with the IBM BPM Configuration Editor

The IBM BPM Configuration editor is a browser-based interface for configuring your new deployment environment. You can graphically edit the configuration properties file that was exported from your source environment by the BPMConfig -migrate command. After you modify the properties file in the editor, you can use the BPMConfig -create command to create a new deployment environment that is based on the modified file.

I used this as source: -


The tool is pre-packaged with BPM 8.5.5 and 8.5.6 ( I'm actually using 8.5.6 ), so it's a simple thing to configure: -

Create a directory into which to place the Editor

mkdir BPMConfigurationEditor

Change to that directory

cd BPMConfigurationEditor

Extract the bundled Editor

unzip /opt/IBM/WebSphere/AppServer/BPM/config/ui/BPMConfigurationEditor.zip

Edit the configuration file

vi configEditor.ini

Add/amend the JAVA_HOME variable

JAVA_HOME=/opt/IBM/WebSphere/AppServer/java

Set the executable bit on the script

chmod +x configEditor.sh

Export the current BPM Deployment Environment

/opt/IBM/WebSphere/AppServer/bin/BPMConfig.sh -export -profile Dmgr01 -de De1 -outputDir /tmp

This results in a number of files: -

-rw-r--r--   1 wasadmin wasadmins  1610 Mar 22 19:38 ltpa.jceks
-rw-r--r--   1 wasadmin wasadmins  1639 Mar 22 19:38 fileRegistry.xml
-rw-r--r--   1 wasadmin wasadmins 13782 Mar 22 19:38 resources-bpc.xml
-rw-r--r--   1 wasadmin wasadmins  7540 Mar 22 19:38 Application-config-bpc.xml
-rw-r--r--   1 wasadmin wasadmins  2621 Mar 22 19:38 ProcessServer_100SourceCustomMerged.xml
-rw-r--r--   1 wasadmin wasadmins  1356 Mar 22 19:38 PDW_100SourceCustomMerged.xml
-rw-r--r--   1 wasadmin wasadmins 84515 Mar 22 19:38 De1.properties


The one in which we are interesting is De1.properties.

Start the editor

Note that this only works against localhost, so one either needs to ensure that a GUI is available on the target server, or pul the De1.properties file back to a client workstation

./configEditor.sh

This returns: -

The configuration editor allows only local access. Specify http://localhost:<port_number>/ibm/bpm/configEditor on the computer where the configuration editor is installed.

and also auto-starts a browser on the target host: -


From here, one can import the required De1.properties file, and then click Open Editor




This gives one the ability to see and, if needed, modify the configuration.

I assume that the updated configuration file could then be saved, and imported back into BPM, perhaps using BPMConfig.sh -update but that's something for another day ....

TP-Link Powerline Adapters - Failing on Pairing

I've just spent ~1 hour trying to get a pair of Powerline adapters to .... pair.

This involved pressing a "Pair" button on one adapter and then running through the house to press the corresponding "Pair" button on its .... pair.

The answer ?

RTFM ( Read The Flippin' Manual )


To paraphrase: -

Step 1:
Press and hold the Pair button of Powerline adapter A for 1 second, the Power LED will start flashing.

Step 2:
In 120 seconds, please press and hold the Pair button of adapter B for 1 second, the Power LED will start flashing. About 60 seconds later, the Powerline LED on both adapters will light up.


The key ?

Yes, press for ONE second.

For the record, I have the TP-Link AV200 WiFi adapter ( with two Ethernet ports ), connected to my TV and my Humax PVR, plus an associated adapter next to my router. I've got another one lurking around somewhere else, connected to my NAS and my Mac Mini.

IBM HTTP Server - GNU Terry Pratchett

I'm probably late to the meme party, but this is what Sir Terry would've wanted: -


achieved with this: -

LoadModule headers_module modules/mod_headers.so
<IfModule headers_module>
header set X-Clacks-Overhead "GNU Terry Pratchett"
</IfModule>


in /opt/IBM/HTTPServer/conf/httpd.conf.

With thanks to this post: -

GNU Terry Pratchett
 

Thursday, 19 March 2015

IBM Business Process Manager - Testing Methodology

This is directly relevant to my current project, hence the current interest :-)


This tutorial is part 1 of IBM Business Process Manager Testing Methodology series. It describes the necessity of IBM® Business Process Manager (BPM) project testing, general testing guidelines and when to test in the IBM BPM project lifecycle. This tutorial shares good practices of IBM BPM project development and helps you get the big picture of quality assurance for business process applications. This series of tutorials describes test methodology for IBM BPM projects. Part 1 describes the necessity of IBM BPM project testing, general testing guidelines, and when to test in the IBM BPM project lifecycle. Part 2 describes details of various testing that should be included in IBM BPM project tests and specific information for environments. Part 3 discusses good testing practices, automation, and testing tools in IBM BPM. This content is part of the IBM Business Process Management Journal.


This tutorial is part 2 of IBM Business Process Manager Testing Methodology series. It describes details of various testing that should be included in IBM® Business Process Manager (BPM) project tests and specific information for environments. This content is part of the IBM Business Process Management Journal.


This tutorial, part 3 of the IBM Business Process Manager Testing Methodology series. It describes good testing practices, including how to make IBM® Business Process Manager (BPM) applications testable, how to conduct IBM BPM automation testing, and what testing tools that can be leveraged in IBM BPM projects. Part 1 and Part 2 of the series discussed the overall testing guidelines, the IBM BPM test lifecycle, and detailed test methods. This content is part of the IBM Business Process Management Journal.

Wednesday, 18 March 2015

IBM Business Process Manager Advanced 8.5.6 - Continuing the build-out

Following my earlier post: -


I'm now building out the configuration for my Process Center

I've taken one of the sample configuration files from here: -

/opt/IBM/WebSphere/AppServer/BPM/samples/config/advanced/Advanced-PC-ThreeClusters-DB2.properties

and amended it to meet my requirements ( I've attached my copy at the bottom of this post ).

I then used BPMConfig to create the Deployment Environment: -

su - wasadmin
/opt/IBM/WebSphere/AppServer/bin/BPMConfig.sh -create -de Advanced-PC-ThreeClusters-DB2.properties 

Logging to file /opt/IBM/WebSphere/AppServer/logs/config/BPMConfig_20150318-173858.log.
Validating the profile registry.
[]
Configuring the deployment manager.
Creating the deployment manager profile.
INSTCONFSUCCESS: Success: Profile Dmgr01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/AboutThisProfile.txt for more information about this profile.
Starting deployment manager profile Dmgr01.
CWUPO0001I: Running configuration action detectNewProducts.ant
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 46599
Configuring managed node profiles.
Creating the managed node Node1 profile.
INSTCONFSUCCESS: Success: Profile AppSrv01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AboutThisProfile.txt for more information about this profile.
Adding the node Node1 to the cell PCCell1.
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
CWPKI0308I: Adding signer alias "CN=bpm855.uk.ibm.com, OU=Root C" to local
           keystore "ClientDefaultTrustStore" with the following SHA digest:
           7B:1F:21:A9:72:6B:7C:2E:58:8B:6A:4B:3C:4D:6E:DB:7F:7D:F2:BE
CWPKI0309I: All signers from remote keystore already exist in local keystore.
ADMU0001I: Begin federation of node Node1 with Deployment Manager at
           bpm855.uk.ibm.com:8879.
ADMU0009I: Successfully connected to Deployment Manager Server:
           bpm855.uk.ibm.com:8879
ADMU0507I: No servers found in configuration under:
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/PCCell1Node1/nodes/Node1/servers
ADMU2010I: Stopping all server processes for node Node1
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: Node1
ADMU0014I: Adding node Node1 configuration to cell: PCCell1
ADMU0016I: Synchronizing configuration between node and cell.


ADMU0300I: The node Node1 was successfully added to the PCCell1 cell.


ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone PCCell1 configuration
           have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the PCCell1 Deployment Manager with
           values from the old cell-level documents.


ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
           the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the PCCell1 cell using wsadmin $AdminApp
           or the Administrative Console.


ADMU0003I: Node Node1 has been successfully federated.
Generating SQL files.
Provisioning cell.
Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.
Configuring the cell.
Configuring the deployment manager.
Provisioning deployment environment.
Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.De1.
Performing security configuration.
Creating clusters.
Configuring data sources.
Configuring the databases.
Configuring clusters.
Configuring cluster MECluster for capability Messaging.
Configuring cluster AppCluster for capability Application.
Operation completed successfully
Configuring cluster SupCluster for capability Support.
Provisioning managed node Node1.
The HTTP and HTTPS ports are added to the virtual hosts list.
Creating cluster members.
Configuring the REST services end points.
Saving configuration changes...
Synchronizing node Node1.
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/syncNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0401I: Begin syncNode operation for node Node1 with Deployment Manager
           bpm855.uk.ibm.com: 8879
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node Node1 has been synchronized with
           Deployment Manager bpm855.uk.ibm.com: 8879
Stopping deployment manager profile Dmgr01.
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/stopServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server dmgr stop completed.

The 'BPMConfig.sh -create -de Advanced-PC-ThreeClusters-DB2.properties' command completed successfully.

and then created my DB2 databases: -

su - db2inst1

cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1/DB2/CMNDB/
./createDatabase.sh 
db2 connect to cmndb
db2 grant dbadm on database to user db2user1
db2 -tvf createSchema_Advanced.sql 
db2 terminate


cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.De1/DB2/CMNDB/
db2 connect to cmndb
db2 -tvf createSchema_Advanced.sql 
db2 -tvf createSchema_Messaging.sql 
db2 terminate


cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.De1/DB2/BPMDB
./createDatabase.sh 
db2 connect to bpmdb
db2 grant dbadm on database to user db2user1
db2 -tvf createSchema_Advanced.sql
db2 -tdGO -vf createProcedure_Advanced.sql
db2 terminate


cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.De1/DB2/PDWDB
./createDatabase.sh 
db2 connect to pdwdb
db2 grant dbadm on database to user db2user1
db2 -tvf createSchema_Advanced.sql
db2 terminate


and then bootstrap the BPM DB: -

su - wasadmin
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/bootstrapProcessServerData.sh -clusterName AppCluster

Bootstraping data into cluster AppCluster and logging into /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/bootstrapProcesServerData.AppCluster.log

WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
'BootstrapProcessServerData admin command completed successfully.....'

and then start the Deployment Environment: -

/opt/IBM/WebSphere/AppServer/bin/BPMConfig.sh -start -profile Dmgr01 -de De1

Logging to file /opt/IBM/WebSphere/AppServer/logs/config/BPMConfig_20150318-185611.log.
Starting deployment manager profile Dmgr01.
CWUPO0001I: Running configuration action detectNewProducts.ant
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 61506
Starting node Node1.
CWUPO0001I: Running configuration action detectNewProducts.ant
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 61908
Starting cluster MECluster.
Starting cluster AppCluster.
Starting cluster SupCluster.
When the BPMConfig command is used to start a deployment environment, it invokes the processes that are used to start the associated clusters. If the command is successful in invoking the processes, it returns a message to report that the command completed successfully. However, to determine whether the cluster members were all started successfully, you need to check the log files of the cluster members. The log files are located in <WAS_HOME>/profiles/logs.
The 'BPMConfig.sh -start -profile Dmgr01 -de De1' command completed successfully.


and watched the logs looking for the infamous "Open for e-business": -

tail -f /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/MEClusterMember1/SystemOut.log

tail -f /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/SupClusterMember1/SystemOut.log

tail -f /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AppClusterMember1/SystemOut.log

and then finally tested Process Center: -





and Process Admin: -



and Performance Admin: -



which is all nice :-)

Advanced-PC-ThreeClusters-DB2.properties

##########################################
# Deployment environment properties: De1 #
##########################################
bpm.de.name=De1
# The type of product configuration: Express, Standard, Advanced, or AdvancedOnly.
bpm.de.type=Advanced
# The type of deployment environment: Process Center or Process Server.
bpm.de.environment=Process Center
# Options: 'true' or 'false'. If false is specified, the database schemas are created when the deployment environment is created. If true is specified, the database schemas must be created manually using the generated scripts, and the bootstrapProcessServerData script must be run manually. When using DB2 for z/OS, the option must be set to true.
bpm.de.deferSchemaCreation=true
# The context root prefix for all web modules in this environment. If set, the context root prefix must start with a forward slash character (/).
bpm.de.contextRootPrefix=
# The virtualHost for all web modules in this environment. If a value is not set for virtualHost, the default value 'default_host' is used.
bpm.de.virtualHost=

######################################################################################################################################################
# Deployment environment administrator authentication alias, it cannot have the same user name as the authentication alias of the cell administrator #
######################################################################################################################################################
bpm.de.authenticationAlias.1.name=DeAdminAlias
bpm.de.authenticationAlias.1.user=deAdmin
bpm.de.authenticationAlias.1.password=password

######################################
# Database user authentication alias #
######################################
bpm.de.authenticationAlias.2.name=BPM_DB_ALIAS
bpm.de.authenticationAlias.2.user=db2user1
bpm.de.authenticationAlias.2.password=passw0rd

#########################################################################################################################################################################################################################################################################################################################################################################################
# The deployment environment administrator role and authentication alias association. If you do not specify the BPMAuthor role, the authentication alias that maps to this role will be used when Process Center connects to IBM Process Server for online deployment. It must be defined in both Process Server and Process Center, and the user names and passwords must be the same. #
#########################################################################################################################################################################################################################################################################################################################################################################################
# Do not modify the name of the role mapping. Role mapping names are predefined. Specify the user name in the authentication alias that corresponds to this role.
bpm.de.roleMapping.1.name=DeAdmin
bpm.de.roleMapping.1.alias=DeAdminAlias

############################
# Cell properties: PCCell1 #
############################
bpm.cell.name=PCCell1
# The database at the cell level. This database is only applicable to IBM BPM Advanced and AdvancedOnly configurations. The value should correspond to the name of a database that is defined in this file.
bpm.cell.db=CellOnlyDb

##################################################
# Cell (WAS) administration authentication alias #
##################################################
bpm.cell.authenticationAlias.1.name=CellAdminAlias
bpm.cell.authenticationAlias.1.user=wasadmin
bpm.cell.authenticationAlias.1.password=passw0rd

##################################################
# Cell role and authentication alias association #
##################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.cell.roleMapping.1.name=CellAdmin
bpm.cell.roleMapping.1.alias=CellAdminAlias



#################################
# Deployment manager properties #
#################################
# The name of the deployment manager node.
bpm.dmgr.nodeName=Dmgr
# The host name of the deployment manager. Do not use localhost for environments that span multiple hosts.
bpm.dmgr.hostname=bpm855.uk.ibm.com
# The installation location of the BPM product. If you want to use a backslash character (\) in your properties file, you must use an escape backslash before it, for example bpm.dmgr.installPath=c:\\IBM\\BPM85.
bpm.dmgr.installPath=/opt/IBM/WebSphere/AppServer
# The name of the deployment manager profile.
bpm.dmgr.profileName=Dmgr01
# Custom options that are passed to the 'manageprofiles' command and used primarily to customize port assignments.
bpm.dmgr.profileOptions=
# To override the default port assignments for this profile, specify a starting port number for generating and assigning ports.
bpm.dmgr.initialPortAssignment=
# The deployment manager SOAP port. This port is used to establish a connection to the deployment manager during the creation of remote nodes. Update this property after you create the deployment manager profile.
bpm.dmgr.soapPort=8879



##################################
# Cluster properties: AppCluster #
##################################
bpm.de.cluster.1.name=AppCluster
# Options: Application, Support, Messaging. These three capabilities correspond to the three-cluster topology that is supported by IBM BPM. If this is a single-cluster environment, specify all three of these capabilities here.
bpm.de.cluster.1.capabilities=Application
# The name of the messaging cluster used by this cluster.
bpm.de.cluster.1.usesMessagingCluster=MECluster
# The name of the support cluster used by this cluster.
bpm.de.cluster.1.usesSupportCluster=SupCluster
# The list of databases that are used on this cluster. Each value should correspond to the name of a database defined in this file. For a single-cluster topology, the list should include all of the databases that are used (with the exception of the CellOnlyDb in IBM BPM Advanced environments). For a three-cluster topology, the Application cluster includes all of the databases except those that are used for messaging and the Performance Data Warehouse (PDW). The messaging and PDW databases are included in the Messaging and Support clusters.
bpm.de.cluster.1.db=ProcessServerDb,SharedDb
bpm.de.cluster.1.capability.1.component.1.name=ProcessPortal
# The context root prefix for all web modules in the specified component. If set, the context root prefix must start with a forward slash character (/).
bpm.de.cluster.1.capability.1.component.1.contextRootPrefix=



#################################
# Cluster properties: MECluster #
#################################
bpm.de.cluster.2.name=MECluster
# Options: Application, Support, Messaging. These three capabilities correspond to the three-cluster topology that is supported by IBM BPM. If this is a single-cluster environment, specify all three of these capabilities here.
bpm.de.cluster.2.capabilities=Messaging
# The list of databases that are used on this cluster. Each value should correspond to the name of a database defined in this file. For a single-cluster topology, the list should include all of the databases that are used (with the exception of the CellOnlyDb in IBM BPM Advanced environments). For a three-cluster topology, the Application cluster includes all of the databases except those that are used for messaging and the Performance Data Warehouse (PDW). The messaging and PDW databases are included in the Messaging and Support clusters.
bpm.de.cluster.2.db=SharedDb



##################################
# Cluster properties: SupCluster #
##################################
bpm.de.cluster.3.name=SupCluster
# Options: Application, Support, Messaging. These three capabilities correspond to the three-cluster topology that is supported by IBM BPM. If this is a single-cluster environment, specify all three of these capabilities here.
bpm.de.cluster.3.capabilities=Support
# The name of the messaging cluster used by this cluster.
bpm.de.cluster.3.usesMessagingCluster=MECluster
# The list of databases that are used on this cluster. Each value should correspond to the name of a database defined in this file. For a single-cluster topology, the list should include all of the databases that are used (with the exception of the CellOnlyDb in IBM BPM Advanced environments). For a three-cluster topology, the Application cluster includes all of the databases except those that are used for messaging and the Performance Data Warehouse (PDW). The messaging and PDW databases are included in the Messaging and Support clusters.
bpm.de.cluster.3.db=PerformanceDb



##########################
# Node properties: Node1 #
##########################
bpm.de.node.1.name=Node1
# If the host name is the same as deployment manager, this node will be created on the same computer. Do not use localhost for environments that span multiple hosts.
bpm.de.node.1.hostname=bpm855.uk.ibm.com
# The installation location of the BPM product. If you want to use a backslash character (\) in your properties file, you must use an escape backslash before it, for example bpm.de.node.1.installPath=c:\\IBM\\BPM85.
bpm.de.node.1.installPath=/opt/IBM/WebSphere/AppServer
# The name of the node profile.
bpm.de.node.1.profileName=AppSrv01
# Custom options that are passed to the 'manageprofiles' command and used primarily to customize port assignments.
bpm.de.node.1.profileOptions=
# To override the default port assignments for this profile, specify a starting port number for generating and assigning ports.
bpm.de.node.1.initialPortAssignment=

################################################
# Cluster member properties: AppClusterMember1 #
################################################
bpm.de.node.1.clusterMember.1.name=AppClusterMember1
# The cluster this cluster member belongs to. This value should correspond to the name of a cluster defined in this file.
bpm.de.node.1.clusterMember.1.cluster=AppCluster
# The proportion of requests that are sent to this cluster member
bpm.de.node.1.clusterMember.1.weight=2
bpm.de.node.1.clusterMember.1.initialPortAssignment=

###############################################
# Cluster member properties: MEClusterMember1 #
###############################################
bpm.de.node.1.clusterMember.2.name=MEClusterMember1
# The cluster this cluster member belongs to. This value should correspond to the name of a cluster defined in this file.
bpm.de.node.1.clusterMember.2.cluster=MECluster
# The proportion of requests that are sent to this cluster member
bpm.de.node.1.clusterMember.2.weight=2
bpm.de.node.1.clusterMember.2.initialPortAssignment=

################################################
# Cluster member properties: SupClusterMember1 #
################################################
bpm.de.node.1.clusterMember.3.name=SupClusterMember1
# The cluster this cluster member belongs to. This value should correspond to the name of a cluster defined in this file.
bpm.de.node.1.clusterMember.3.cluster=SupCluster
# The proportion of requests that are sent to this cluster member
bpm.de.node.1.clusterMember.3.weight=2
bpm.de.node.1.clusterMember.3.initialPortAssignment=

#################################
# Database properties: SharedDb #
#################################
# Keyword to use to refer to this set of database properties. This is not the database name.
bpm.de.db.1.name=SharedDb
# The list of available options depends on the product configuration. For IBM BPM Express and Standard, the options are ProcessServer, EmbeddedECM, PDW, Messaging, and BusinessSpace. For IBM BPM Advanced, the options are ProcessServer, EmbeddedECM, PDW, CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For IBM BPM Advanced Only, the options are CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For EmbeddedECM, there is no support if the operating system for the IBM BPM environment is z/OS.
bpm.de.db.1.dbCapabilities=Messaging,BusinessSpace,CommonDB,BPC
# Options: DB2, DB2zOS, Oracle, or SQL Server.
bpm.de.db.1.type=DB2
# The host name of the database. Do not use localhost for environments that span multiple hosts.
bpm.de.db.1.hostname=bpm855.uk.ibm.com
bpm.de.db.1.portNumber=60012
# The name of the database.
bpm.de.db.1.databaseName=CMNDB
bpm.de.db.1.schema=db2user1

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.1.roleMapping.1.name=DbUser
bpm.de.db.1.roleMapping.1.alias=BPM_DB_ALIAS

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.1.roleMapping.2.name=DbUserXAR
bpm.de.db.1.roleMapping.2.alias=BPM_DB_ALIAS



########################################
# Database properties: ProcessServerDb #
########################################
# Keyword to use to refer to this set of database properties. This is not the database name.
bpm.de.db.2.name=ProcessServerDb
# The list of available options depends on the product configuration. For IBM BPM Express and Standard, the options are ProcessServer, EmbeddedECM, PDW, Messaging, and BusinessSpace. For IBM BPM Advanced, the options are ProcessServer, EmbeddedECM, PDW, CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For IBM BPM Advanced Only, the options are CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For EmbeddedECM, there is no support if the operating system for the IBM BPM environment is z/OS.
bpm.de.db.2.dbCapabilities=ProcessServer,EmbeddedECM
# Options: DB2, DB2zOS, Oracle, or SQL Server.
bpm.de.db.2.type=DB2
# The host name of the database. Do not use localhost for environments that span multiple hosts.
bpm.de.db.2.hostname=bpm855.uk.ibm.com
bpm.de.db.2.portNumber=60012
# The name of the database.
bpm.de.db.2.databaseName=BPMDB
bpm.de.db.2.schema=db2user1

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.2.roleMapping.1.name=DbUser
bpm.de.db.2.roleMapping.1.alias=BPM_DB_ALIAS

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.2.roleMapping.2.name=DbUserXAR
bpm.de.db.2.roleMapping.2.alias=BPM_DB_ALIAS



######################################
# Database properties: PerformanceDb #
######################################
# Keyword to use to refer to this set of database properties. This is not the database name.
bpm.de.db.3.name=PerformanceDb
# The list of available options depends on the product configuration. For IBM BPM Express and Standard, the options are ProcessServer, EmbeddedECM, PDW, Messaging, and BusinessSpace. For IBM BPM Advanced, the options are ProcessServer, EmbeddedECM, PDW, CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For IBM BPM Advanced Only, the options are CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For EmbeddedECM, there is no support if the operating system for the IBM BPM environment is z/OS.
bpm.de.db.3.dbCapabilities=PDW
# Options: DB2, DB2zOS, Oracle, or SQL Server.
bpm.de.db.3.type=DB2
# The host name of the database. Do not use localhost for environments that span multiple hosts.
bpm.de.db.3.hostname=bpm855.uk.ibm.com
bpm.de.db.3.portNumber=60012
# The name of the database.
bpm.de.db.3.databaseName=PDWDB
bpm.de.db.3.schema=db2user1

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.3.roleMapping.1.name=DbUser
bpm.de.db.3.roleMapping.1.alias=BPM_DB_ALIAS

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.3.roleMapping.2.name=DbUserXAR
bpm.de.db.3.roleMapping.2.alias=BPM_DB_ALIAS



###################################
# Database properties: CellOnlyDb #
###################################
# Keyword to use to refer to this set of database properties. This is not the database name.
bpm.de.db.4.name=CellOnlyDb
# The list of available options depends on the product configuration. For IBM BPM Express and Standard, the options are ProcessServer, EmbeddedECM, PDW, Messaging, and BusinessSpace. For IBM BPM Advanced, the options are ProcessServer, EmbeddedECM, PDW, CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For IBM BPM Advanced Only, the options are CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For EmbeddedECM, there is no support if the operating system for the IBM BPM environment is z/OS.
bpm.de.db.4.dbCapabilities=CellScopedDB
# Options: DB2, DB2zOS, Oracle, or SQL Server.
bpm.de.db.4.type=DB2
# The host name of the database. Do not use localhost for environments that span multiple hosts.
bpm.de.db.4.hostname=bpm855.uk.ibm.com
bpm.de.db.4.portNumber=60012
# The name of the database.
bpm.de.db.4.databaseName=CMNDB
bpm.de.db.4.schema=db2user1

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.4.roleMapping.1.name=DbUser
bpm.de.db.4.roleMapping.1.alias=BPM_DB_ALIAS

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.4.roleMapping.2.name=DbUserXAR
bpm.de.db.4.roleMapping.2.alias=BPM_DB_ALIAS



IBM Business Process Manager Advanced 8.5.6 - Continuing the build-out

Following my earlier post: -


I'm now building out the configuration for my Process Center

I've taken one of the sample configuration files from here: -

/opt/IBM/WebSphere/AppServer/BPM/samples/config/advanced/Advanced-PC-ThreeClusters-DB2.properties

and amended it to meet my requirements ( I've attached my copy at the bottom of this post ).

I then used BPMConfig to create the Deployment Environment: -

su - wasadmin
/opt/IBM/WebSphere/AppServer/bin/BPMConfig.sh -create -de Advanced-PC-ThreeClusters-DB2.properties 

Logging to file /opt/IBM/WebSphere/AppServer/logs/config/BPMConfig_20150318-173858.log.
Validating the profile registry.
[]
Configuring the deployment manager.
Creating the deployment manager profile.
INSTCONFSUCCESS: Success: Profile Dmgr01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/AboutThisProfile.txt for more information about this profile.
Starting deployment manager profile Dmgr01.
CWUPO0001I: Running configuration action detectNewProducts.ant
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 46599
Configuring managed node profiles.
Creating the managed node Node1 profile.
INSTCONFSUCCESS: Success: Profile AppSrv01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AboutThisProfile.txt for more information about this profile.
Adding the node Node1 to the cell PCCell1.
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
CWPKI0308I: Adding signer alias "CN=bpm855.uk.ibm.com, OU=Root C" to local
           keystore "ClientDefaultTrustStore" with the following SHA digest:
           7B:1F:21:A9:72:6B:7C:2E:58:8B:6A:4B:3C:4D:6E:DB:7F:7D:F2:BE
CWPKI0309I: All signers from remote keystore already exist in local keystore.
ADMU0001I: Begin federation of node Node1 with Deployment Manager at
           bpm855.uk.ibm.com:8879.
ADMU0009I: Successfully connected to Deployment Manager Server:
           bpm855.uk.ibm.com:8879
ADMU0507I: No servers found in configuration under:
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/PCCell1Node1/nodes/Node1/servers
ADMU2010I: Stopping all server processes for node Node1
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: Node1
ADMU0014I: Adding node Node1 configuration to cell: PCCell1
ADMU0016I: Synchronizing configuration between node and cell.


ADMU0300I: The node Node1 was successfully added to the PCCell1 cell.


ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone PCCell1 configuration
           have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the PCCell1 Deployment Manager with
           values from the old cell-level documents.


ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
           the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the PCCell1 cell using wsadmin $AdminApp
           or the Administrative Console.


ADMU0003I: Node Node1 has been successfully federated.
Generating SQL files.
Provisioning cell.
Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.
Configuring the cell.
Configuring the deployment manager.
Provisioning deployment environment.
Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.De1.
Performing security configuration.
Creating clusters.
Configuring data sources.
Configuring the databases.
Configuring clusters.
Configuring cluster MECluster for capability Messaging.
Configuring cluster AppCluster for capability Application.
Operation completed successfully
Configuring cluster SupCluster for capability Support.
Provisioning managed node Node1.
The HTTP and HTTPS ports are added to the virtual hosts list.
Creating cluster members.
Configuring the REST services end points.
Saving configuration changes...
Synchronizing node Node1.
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/syncNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0401I: Begin syncNode operation for node Node1 with Deployment Manager
           bpm855.uk.ibm.com: 8879
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node Node1 has been synchronized with
           Deployment Manager bpm855.uk.ibm.com: 8879
Stopping deployment manager profile Dmgr01.
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/stopServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server dmgr stop completed.

The 'BPMConfig.sh -create -de Advanced-PC-ThreeClusters-DB2.properties' command completed successfully.

and then created my DB2 databases: -

su - db2inst1

cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1/DB2/CMNDB/
./createDatabase.sh 
db2 connect to cmndb
db2 grant dbadm on database to user db2user1
db2 -tvf createSchema_Advanced.sql 
db2 terminate


cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.De1/DB2/CMNDB/
db2 connect to cmndb
db2 -tvf createSchema_Advanced.sql 
db2 -tvf createSchema_Messaging.sql 
db2 terminate


cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.De1/DB2/BPMDB
./createDatabase.sh 
db2 connect to bpmdb
db2 grant dbadm on database to user db2user1
db2 -tvf createSchema_Advanced.sql
db2 -tdGO -vf createProcedure_Advanced.sql
db2 terminate


cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/PCCell1.De1/DB2/PDWDB
./createDatabase.sh 
db2 connect to pdwdb
db2 grant dbadm on database to user db2user1
db2 -tvf createSchema_Advanced.sql
db2 terminate


and then bootstrap the BPM DB: -

su - wasadmin
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/bootstrapProcessServerData.sh -clusterName AppCluster

Bootstraping data into cluster AppCluster and logging into /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/bootstrapProcesServerData.AppCluster.log

WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
'BootstrapProcessServerData admin command completed successfully.....'

and then start the Deployment Environment: -

/opt/IBM/WebSphere/AppServer/bin/BPMConfig.sh -start -profile Dmgr01 -de De1

Logging to file /opt/IBM/WebSphere/AppServer/logs/config/BPMConfig_20150318-185611.log.
Starting deployment manager profile Dmgr01.
CWUPO0001I: Running configuration action detectNewProducts.ant
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 61506
Starting node Node1.
CWUPO0001I: Running configuration action detectNewProducts.ant
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 61908
Starting cluster MECluster.
Starting cluster AppCluster.
Starting cluster SupCluster.
When the BPMConfig command is used to start a deployment environment, it invokes the processes that are used to start the associated clusters. If the command is successful in invoking the processes, it returns a message to report that the command completed successfully. However, to determine whether the cluster members were all started successfully, you need to check the log files of the cluster members. The log files are located in <WAS_HOME>/profiles/logs.
The 'BPMConfig.sh -start -profile Dmgr01 -de De1' command completed successfully.


and watched the logs looking for the infamous "Open for e-business": -

tail -f /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/MEClusterMember1/SystemOut.log

tail -f /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/SupClusterMember1/SystemOut.log

tail -f /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AppClusterMember1/SystemOut.log

and then finally tested Process Center: -





and Process Admin: -



and Performance Admin: -



which is all nice :-)

Advanced-PC-ThreeClusters-DB2.properties

##########################################
# Deployment environment properties: De1 #
##########################################
bpm.de.name=De1
# The type of product configuration: Express, Standard, Advanced, or AdvancedOnly.
bpm.de.type=Advanced
# The type of deployment environment: Process Center or Process Server.
bpm.de.environment=Process Center
# Options: 'true' or 'false'. If false is specified, the database schemas are created when the deployment environment is created. If true is specified, the database schemas must be created manually using the generated scripts, and the bootstrapProcessServerData script must be run manually. When using DB2 for z/OS, the option must be set to true.
bpm.de.deferSchemaCreation=true
# The context root prefix for all web modules in this environment. If set, the context root prefix must start with a forward slash character (/).
bpm.de.contextRootPrefix=
# The virtualHost for all web modules in this environment. If a value is not set for virtualHost, the default value 'default_host' is used.
bpm.de.virtualHost=

######################################################################################################################################################
# Deployment environment administrator authentication alias, it cannot have the same user name as the authentication alias of the cell administrator #
######################################################################################################################################################
bpm.de.authenticationAlias.1.name=DeAdminAlias
bpm.de.authenticationAlias.1.user=deAdmin
bpm.de.authenticationAlias.1.password=password

######################################
# Database user authentication alias #
######################################
bpm.de.authenticationAlias.2.name=BPM_DB_ALIAS
bpm.de.authenticationAlias.2.user=db2user1
bpm.de.authenticationAlias.2.password=passw0rd

#########################################################################################################################################################################################################################################################################################################################################################################################
# The deployment environment administrator role and authentication alias association. If you do not specify the BPMAuthor role, the authentication alias that maps to this role will be used when Process Center connects to IBM Process Server for online deployment. It must be defined in both Process Server and Process Center, and the user names and passwords must be the same. #
#########################################################################################################################################################################################################################################################################################################################################################################################
# Do not modify the name of the role mapping. Role mapping names are predefined. Specify the user name in the authentication alias that corresponds to this role.
bpm.de.roleMapping.1.name=DeAdmin
bpm.de.roleMapping.1.alias=DeAdminAlias

############################
# Cell properties: PCCell1 #
############################
bpm.cell.name=PCCell1
# The database at the cell level. This database is only applicable to IBM BPM Advanced and AdvancedOnly configurations. The value should correspond to the name of a database that is defined in this file.
bpm.cell.db=CellOnlyDb

##################################################
# Cell (WAS) administration authentication alias #
##################################################
bpm.cell.authenticationAlias.1.name=CellAdminAlias
bpm.cell.authenticationAlias.1.user=wasadmin
bpm.cell.authenticationAlias.1.password=passw0rd

##################################################
# Cell role and authentication alias association #
##################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.cell.roleMapping.1.name=CellAdmin
bpm.cell.roleMapping.1.alias=CellAdminAlias



#################################
# Deployment manager properties #
#################################
# The name of the deployment manager node.
bpm.dmgr.nodeName=Dmgr
# The host name of the deployment manager. Do not use localhost for environments that span multiple hosts.
bpm.dmgr.hostname=bpm855.uk.ibm.com
# The installation location of the BPM product. If you want to use a backslash character (\) in your properties file, you must use an escape backslash before it, for example bpm.dmgr.installPath=c:\\IBM\\BPM85.
bpm.dmgr.installPath=/opt/IBM/WebSphere/AppServer
# The name of the deployment manager profile.
bpm.dmgr.profileName=Dmgr01
# Custom options that are passed to the 'manageprofiles' command and used primarily to customize port assignments.
bpm.dmgr.profileOptions=
# To override the default port assignments for this profile, specify a starting port number for generating and assigning ports.
bpm.dmgr.initialPortAssignment=
# The deployment manager SOAP port. This port is used to establish a connection to the deployment manager during the creation of remote nodes. Update this property after you create the deployment manager profile.
bpm.dmgr.soapPort=8879



##################################
# Cluster properties: AppCluster #
##################################
bpm.de.cluster.1.name=AppCluster
# Options: Application, Support, Messaging. These three capabilities correspond to the three-cluster topology that is supported by IBM BPM. If this is a single-cluster environment, specify all three of these capabilities here.
bpm.de.cluster.1.capabilities=Application
# The name of the messaging cluster used by this cluster.
bpm.de.cluster.1.usesMessagingCluster=MECluster
# The name of the support cluster used by this cluster.
bpm.de.cluster.1.usesSupportCluster=SupCluster
# The list of databases that are used on this cluster. Each value should correspond to the name of a database defined in this file. For a single-cluster topology, the list should include all of the databases that are used (with the exception of the CellOnlyDb in IBM BPM Advanced environments). For a three-cluster topology, the Application cluster includes all of the databases except those that are used for messaging and the Performance Data Warehouse (PDW). The messaging and PDW databases are included in the Messaging and Support clusters.
bpm.de.cluster.1.db=ProcessServerDb,SharedDb
bpm.de.cluster.1.capability.1.component.1.name=ProcessPortal
# The context root prefix for all web modules in the specified component. If set, the context root prefix must start with a forward slash character (/).
bpm.de.cluster.1.capability.1.component.1.contextRootPrefix=



#################################
# Cluster properties: MECluster #
#################################
bpm.de.cluster.2.name=MECluster
# Options: Application, Support, Messaging. These three capabilities correspond to the three-cluster topology that is supported by IBM BPM. If this is a single-cluster environment, specify all three of these capabilities here.
bpm.de.cluster.2.capabilities=Messaging
# The list of databases that are used on this cluster. Each value should correspond to the name of a database defined in this file. For a single-cluster topology, the list should include all of the databases that are used (with the exception of the CellOnlyDb in IBM BPM Advanced environments). For a three-cluster topology, the Application cluster includes all of the databases except those that are used for messaging and the Performance Data Warehouse (PDW). The messaging and PDW databases are included in the Messaging and Support clusters.
bpm.de.cluster.2.db=SharedDb



##################################
# Cluster properties: SupCluster #
##################################
bpm.de.cluster.3.name=SupCluster
# Options: Application, Support, Messaging. These three capabilities correspond to the three-cluster topology that is supported by IBM BPM. If this is a single-cluster environment, specify all three of these capabilities here.
bpm.de.cluster.3.capabilities=Support
# The name of the messaging cluster used by this cluster.
bpm.de.cluster.3.usesMessagingCluster=MECluster
# The list of databases that are used on this cluster. Each value should correspond to the name of a database defined in this file. For a single-cluster topology, the list should include all of the databases that are used (with the exception of the CellOnlyDb in IBM BPM Advanced environments). For a three-cluster topology, the Application cluster includes all of the databases except those that are used for messaging and the Performance Data Warehouse (PDW). The messaging and PDW databases are included in the Messaging and Support clusters.
bpm.de.cluster.3.db=PerformanceDb



##########################
# Node properties: Node1 #
##########################
bpm.de.node.1.name=Node1
# If the host name is the same as deployment manager, this node will be created on the same computer. Do not use localhost for environments that span multiple hosts.
bpm.de.node.1.hostname=bpm855.uk.ibm.com
# The installation location of the BPM product. If you want to use a backslash character (\) in your properties file, you must use an escape backslash before it, for example bpm.de.node.1.installPath=c:\\IBM\\BPM85.
bpm.de.node.1.installPath=/opt/IBM/WebSphere/AppServer
# The name of the node profile.
bpm.de.node.1.profileName=AppSrv01
# Custom options that are passed to the 'manageprofiles' command and used primarily to customize port assignments.
bpm.de.node.1.profileOptions=
# To override the default port assignments for this profile, specify a starting port number for generating and assigning ports.
bpm.de.node.1.initialPortAssignment=

################################################
# Cluster member properties: AppClusterMember1 #
################################################
bpm.de.node.1.clusterMember.1.name=AppClusterMember1
# The cluster this cluster member belongs to. This value should correspond to the name of a cluster defined in this file.
bpm.de.node.1.clusterMember.1.cluster=AppCluster
# The proportion of requests that are sent to this cluster member
bpm.de.node.1.clusterMember.1.weight=2
bpm.de.node.1.clusterMember.1.initialPortAssignment=

###############################################
# Cluster member properties: MEClusterMember1 #
###############################################
bpm.de.node.1.clusterMember.2.name=MEClusterMember1
# The cluster this cluster member belongs to. This value should correspond to the name of a cluster defined in this file.
bpm.de.node.1.clusterMember.2.cluster=MECluster
# The proportion of requests that are sent to this cluster member
bpm.de.node.1.clusterMember.2.weight=2
bpm.de.node.1.clusterMember.2.initialPortAssignment=

################################################
# Cluster member properties: SupClusterMember1 #
################################################
bpm.de.node.1.clusterMember.3.name=SupClusterMember1
# The cluster this cluster member belongs to. This value should correspond to the name of a cluster defined in this file.
bpm.de.node.1.clusterMember.3.cluster=SupCluster
# The proportion of requests that are sent to this cluster member
bpm.de.node.1.clusterMember.3.weight=2
bpm.de.node.1.clusterMember.3.initialPortAssignment=

#################################
# Database properties: SharedDb #
#################################
# Keyword to use to refer to this set of database properties. This is not the database name.
bpm.de.db.1.name=SharedDb
# The list of available options depends on the product configuration. For IBM BPM Express and Standard, the options are ProcessServer, EmbeddedECM, PDW, Messaging, and BusinessSpace. For IBM BPM Advanced, the options are ProcessServer, EmbeddedECM, PDW, CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For IBM BPM Advanced Only, the options are CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For EmbeddedECM, there is no support if the operating system for the IBM BPM environment is z/OS.
bpm.de.db.1.dbCapabilities=Messaging,BusinessSpace,CommonDB,BPC
# Options: DB2, DB2zOS, Oracle, or SQL Server.
bpm.de.db.1.type=DB2
# The host name of the database. Do not use localhost for environments that span multiple hosts.
bpm.de.db.1.hostname=bpm855.uk.ibm.com
bpm.de.db.1.portNumber=60012
# The name of the database.
bpm.de.db.1.databaseName=CMNDB
bpm.de.db.1.schema=db2user1

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.1.roleMapping.1.name=DbUser
bpm.de.db.1.roleMapping.1.alias=BPM_DB_ALIAS

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.1.roleMapping.2.name=DbUserXAR
bpm.de.db.1.roleMapping.2.alias=BPM_DB_ALIAS



########################################
# Database properties: ProcessServerDb #
########################################
# Keyword to use to refer to this set of database properties. This is not the database name.
bpm.de.db.2.name=ProcessServerDb
# The list of available options depends on the product configuration. For IBM BPM Express and Standard, the options are ProcessServer, EmbeddedECM, PDW, Messaging, and BusinessSpace. For IBM BPM Advanced, the options are ProcessServer, EmbeddedECM, PDW, CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For IBM BPM Advanced Only, the options are CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For EmbeddedECM, there is no support if the operating system for the IBM BPM environment is z/OS.
bpm.de.db.2.dbCapabilities=ProcessServer,EmbeddedECM
# Options: DB2, DB2zOS, Oracle, or SQL Server.
bpm.de.db.2.type=DB2
# The host name of the database. Do not use localhost for environments that span multiple hosts.
bpm.de.db.2.hostname=bpm855.uk.ibm.com
bpm.de.db.2.portNumber=60012
# The name of the database.
bpm.de.db.2.databaseName=BPMDB
bpm.de.db.2.schema=db2user1

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.2.roleMapping.1.name=DbUser
bpm.de.db.2.roleMapping.1.alias=BPM_DB_ALIAS

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.2.roleMapping.2.name=DbUserXAR
bpm.de.db.2.roleMapping.2.alias=BPM_DB_ALIAS



######################################
# Database properties: PerformanceDb #
######################################
# Keyword to use to refer to this set of database properties. This is not the database name.
bpm.de.db.3.name=PerformanceDb
# The list of available options depends on the product configuration. For IBM BPM Express and Standard, the options are ProcessServer, EmbeddedECM, PDW, Messaging, and BusinessSpace. For IBM BPM Advanced, the options are ProcessServer, EmbeddedECM, PDW, CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For IBM BPM Advanced Only, the options are CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For EmbeddedECM, there is no support if the operating system for the IBM BPM environment is z/OS.
bpm.de.db.3.dbCapabilities=PDW
# Options: DB2, DB2zOS, Oracle, or SQL Server.
bpm.de.db.3.type=DB2
# The host name of the database. Do not use localhost for environments that span multiple hosts.
bpm.de.db.3.hostname=bpm855.uk.ibm.com
bpm.de.db.3.portNumber=60012
# The name of the database.
bpm.de.db.3.databaseName=PDWDB
bpm.de.db.3.schema=db2user1

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.3.roleMapping.1.name=DbUser
bpm.de.db.3.roleMapping.1.alias=BPM_DB_ALIAS

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.3.roleMapping.2.name=DbUserXAR
bpm.de.db.3.roleMapping.2.alias=BPM_DB_ALIAS



###################################
# Database properties: CellOnlyDb #
###################################
# Keyword to use to refer to this set of database properties. This is not the database name.
bpm.de.db.4.name=CellOnlyDb
# The list of available options depends on the product configuration. For IBM BPM Express and Standard, the options are ProcessServer, EmbeddedECM, PDW, Messaging, and BusinessSpace. For IBM BPM Advanced, the options are ProcessServer, EmbeddedECM, PDW, CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For IBM BPM Advanced Only, the options are CellScopedDB, Messaging, BusinessSpace, CommonDB, and BPC. For EmbeddedECM, there is no support if the operating system for the IBM BPM environment is z/OS.
bpm.de.db.4.dbCapabilities=CellScopedDB
# Options: DB2, DB2zOS, Oracle, or SQL Server.
bpm.de.db.4.type=DB2
# The host name of the database. Do not use localhost for environments that span multiple hosts.
bpm.de.db.4.hostname=bpm855.uk.ibm.com
bpm.de.db.4.portNumber=60012
# The name of the database.
bpm.de.db.4.databaseName=CMNDB
bpm.de.db.4.schema=db2user1

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.4.roleMapping.1.name=DbUser
bpm.de.db.4.roleMapping.1.alias=BPM_DB_ALIAS

#######################################################
# Database role and authentication alias associations #
#######################################################
# Do not modify this value. Role mapping names are predefined. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.4.roleMapping.2.name=DbUserXAR
bpm.de.db.4.roleMapping.2.alias=BPM_DB_ALIAS