Appreciations accepted

Vladlen Litvinov, the author: If you have some job offer for me, I'm ready to discuss it. View Vladlen Litvinov's profile on LinkedIn

Password

Thursday, February 13, 2014

How to install a stand-alone installation in IBM BPM 8.5 (Part 2 - Process Server).

We will go the same way. All the steps are identically.

http://bpmadmin.blogspot.com/2013/12/how-to-install-stand-alone-installation.html

The difference in properties file only. We only added the settings of our Process Center and changed settings of DB, hosts etc.

Our file is: Express-PS-Standalone-Oracle.properties

##############################################
# Deployment environment basic properties.   #
##############################################
bpm.de.name=BPMEXPPS
# Options: true, false If this is set false, database tables are created during deployment environment creation when BPMConfig is run with the create de action . If set to true, the tables need to be created manually.
bpm.de.deferSchemaCreation=true
# Type of product configuration: Express, Standard, Advanced or AdvancedOnly
bpm.de.type=Express
# Type of deployment environment: Process Center or Process Server
bpm.de.environment=Process Server
bpm.de.psServerName=BPMEXPSProcessServer
# The intended purpose for this deployment environment. Options: Test, Staging, Production
bpm.de.psPurpose=Test
# Options: true, false. Set to false if the Process Server is online and can be connected to the Process Center
bpm.de.psOffline=false
# The transport protocol to access the Process Center specified above. Options: http or https.
bpm.de.psProcessCenterTransportProtocol=http
# The host name of the Process Center specified  above.
bpm.de.psProcessCenterHostname=server
# The port number for the Process Center specified above.
bpm.de.psProcessCenterPort=9082
################################################################
# Deployment environment administrator authentication alias.   #
################################################################
bpm.de.authenticationAlias.1.name=DeAdminAlias
bpm.de.authenticationAlias.1.user=wasadmin
bpm.de.authenticationAlias.1.password=wasadmin
#############################################################
# Database user authentication alias for common database.   #
#############################################################
bpm.de.authenticationAlias.2.name=BPM_DB_CMN_ALIAS
bpm.de.authenticationAlias.2.user=EXPCMNDBPS
bpm.de.authenticationAlias.2.password=Password
#####################################################################
# Database user authentication alias for process server database.   #
#####################################################################
bpm.de.authenticationAlias.3.name=BPM_DB_PS_ALIAS
bpm.de.authenticationAlias.3.user=EXPBPMDBPS
bpm.de.authenticationAlias.3.password=Password
#################################################################################
# Database user authentication alias for performance data warehouse database.   #
#################################################################################
bpm.de.authenticationAlias.4.name=BPM_DB_PDW_ALIAS
bpm.de.authenticationAlias.4.user=EXPPDWDBPS
bpm.de.authenticationAlias.4.password=Password
####################################################################################
# Deployment Environment Administrator role and authentication alias association   #
####################################################################################
# bpm.de.roleMapping.DeAdmin.name
bpm.de.roleMapping.1.name=DeAdmin
bpm.de.roleMapping.1.alias=DeAdminAlias
#####################
# Cell properties   #
#####################
bpm.cell.name=PSCellExp
####################################################
# Cell (WAS) administration authentication alias   #
####################################################
bpm.cell.authenticationAlias.1.name=CellAdminAlias
bpm.cell.authenticationAlias.1.user=admin
bpm.cell.authenticationAlias.1.password=admin
####################################################
# Cell role and authentication alias association   #
####################################################
# Role mapping names are pre-defined. Do not modify this value. Specify the user name in the authentication alias corresponding to this role.
bpm.cell.roleMapping.1.name=CellAdmin
bpm.cell.roleMapping.1.alias=CellAdminAlias
##############################
# Properties for each node   #
##############################
bpm.de.node.1.name=Node1
# If the hostname is the same as deployment manager, this node will be created on the same computer. Do not use localhost for environments that are spread across multiple machines.
bpm.de.node.1.hostname=server2
bpm.de.node.1.installPath=/opt/ibm/BPM85Exp
bpm.de.node.1.profileName=ProcSrv01
bpm.de.node.1.initialPortAssignment=
bpm.de.node.1.server.db=ProcessServerDb,SharedDb,PerformanceDb
#########################
# Database properties   #
#########################
# Keyword to use to  refer to this set of database properties. This is not the database name.
bpm.de.db.1.name=SharedDb
# List of components that are configured on this database. For Advanced configurations the options are: Messaging, BusinessSpace, CommonDB, BPC and CellScopedDB. For Standard and Express configurations, the options are: Messaging, BusinessSpace, ProcessServer, EmbeddedECM and PDW.
bpm.de.db.1.dbCapabilities=Messaging,BusinessSpace
# Database name.
bpm.de.db.1.databaseName=BPM8
# Database type. Options: DB2, DB2zOS, Oracle or SQLServer
bpm.de.db.1.type=Oracle
# Database hostname. Do not use localhost for environments that are spread across multiple machines.
bpm.de.db.1.hostname=server
bpm.de.db.1.portNumber=1521
bpm.de.db.1.sqlServerWinAuth=false
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. 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_CMN_ALIAS
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. 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_CMN_ALIAS
bpm.de.db.1.schema=EXPCMNDBPS
#########################
# Database properties   #
#########################
# Keyword to use to  refer to this set of database properties. This is not the database name.
bpm.de.db.2.name=ProcessServerDb
# List of components that are configured on this database. For Advanced configurations the options are: Messaging, BusinessSpace, CommonDB, BPC and CellScopedDB. For Standard and Express configurations, the options are: Messaging, BusinessSpace, ProcessServer, EmbeddedECM and PDW.
bpm.de.db.2.dbCapabilities=ProcessServer,EmbeddedECM
# Database name.
bpm.de.db.2.databaseName=BPM8
# Database type. Options: DB2, DB2zOS, Oracle or SQLServer
bpm.de.db.2.type=Oracle
# Database hostname. Do not use localhost for environments that are spread across multiple machines.
bpm.de.db.2.hostname=server
bpm.de.db.2.portNumber=1521
bpm.de.db.2.sqlServerWinAuth=false
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. 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_PS_ALIAS
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. 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_PS_ALIAS
bpm.de.db.2.schema=EXPBPMDBPS
#########################
# Database properties   #
#########################
# Keyword to use to  refer to this set of database properties. This is not the database name.
bpm.de.db.3.name=PerformanceDb
# List of components that are configured on this database. For Advanced configurations the options are: Messaging, BusinessSpace, CommonDB, BPC and CellScopedDB. For Standard and Express configurations, the options are: Messaging, BusinessSpace, ProcessServer, EmbeddedECM and PDW.
bpm.de.db.3.dbCapabilities=PDW
# Database name.
bpm.de.db.3.databaseName=BPM8
# Database type. Options: DB2, DB2zOS, Oracle or SQLServer
bpm.de.db.3.type=Oracle
# Database hostname. Do not use localhost for environments that are spread across multiple machines.
bpm.de.db.3.hostname=server
bpm.de.db.3.portNumber=1521
bpm.de.db.3.sqlServerWinAuth=false
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. 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_PDW_ALIAS
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. 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_PDW_ALIAS
bpm.de.db.3.schema=EXPPDWDBPS

5 comments:

  1. I have a query. I have a VM with stand alone installation of BPM 8.5. There is no process server there but there is just WAS. But i can successfully run process instances through process portal during testing. So it means process apps run on WAS only so then why we need to add process server online and offline when WAS is enough ?

    ReplyDelete
    Replies
    1. Hi Haider,
      I will try explain your misunderstanding more shortly.
      You cannot run process applications using "WAS only".
      You wrote that you have an installation of BPM. I think you have Process Center component. It is development environment. It contains a repository for storing process applications etc and runtime for running process applications (or Process Server).
      When some process application is ready for using it is installed on "pure" Process Server as Test, Stage or Production environment. These environments need not any repositories because there is no version control there and so on. Usually Test is online, Stage and Prod are offline.
      So if you use BPM for development only - you need not separate Process Server.
      But, on the contrary, full BPM architecture must include both Process Center and Process Servers.

      Delete
    2. Hi Vladlen,

      Thanks a lot for clearing all this. I had this confusion. Yes I have an environment for development with Process Center. 1 question remains: so what is there in the runtime for running process applications - is underline there is a process server. If we must have process server for test, staging and production so where is process server in dev environment as I only see WAS/BPM with Process Center/DB2 as main installation steps. As I am able to run instances of process apps it means that this dev runtime has a hidden process server in it ? am i write ... ?

      Delete
    3. One more time - Process Center contains Process Server but it is not pointed separately. Process Center is undivided component.

      Delete