Installing and configuring initially for an offline Process Server

There is one primary script file to install and configure IBM® Stewardship Center for a Process Center installation with an offline process server.

About this task

The primary script file calls a set of secondary script files. The first time that you install and configure IBM Stewardship Center, you specify a target and all of the secondary script files are automatically run.

Procedure

  1. In the Process Center environment, import the Process application into the Process center and create the offline packages for the Process applications by extracting the installation packages into the file system under the STEWARDSHIP_CENTER_INSTALL_HOME/mdmg directory of the Process Center.
    Use the target get_installable_packages_offline_server as shown in the following examples:
    • Windows
      InstallGovernanceApplication.bat
      get_installable_packages_offline_server
    • Linux or UNIX
      InstallGovernanceApplication.sh
      get_installable_packages_offline_server
    The following actions are performed when you run the script file with this target:
    • Import the IBM Stewardship Center process applications into Process Center environment.
    • Create the offline packages for the imported IBM Stewardship Center Process Applications
    • Extracts the offline packages of the Process applications to the File system of the Process Center
  2. Once the installation packages are extracted to the Process Center file system, copy the STEWARDSHIP_CENTER_INSTALL_HOME/mdmg directory to the Server machine where offline Process Server is installed.
  3. DB2® database only: If you plan to install IBM Stewardship Center on a computer that is separate from the InfoSphere® MDM database:
    1. Install the DB2 client on the separate computer
    2. Catalog the InfoSphere MDM database.
    3. Ensure that the MDM database is accessible.
    Performing these steps ensures that the computer where IBM Stewardship Center is installed can connect to the InfoSphere MDM database.
  4. On the computer where the IBM Stewardship Center installation files were downloaded, run the primary script file on the IBM BPM application server. Use the target install_configure_governance_apps as shown in the following examples:
    Windows
    InstallGovernanceApplication.bat install_configure_governance_apps_offline_server
    Linux® or UNIX
    InstallGovernanceApplication.sh install_configure_governance_apps_offline_server
    The following actions are performed when you run the primary script file with this target:
    • Set up the InfoSphere MDM application server
    • Physical MDM: Add the metadata for the suspected duplicate process applications
    • Restart the InfoSphere MDM application server
    • Set up the IBM Business Process Manager application server
    • Install the IBM Stewardship Center Process applications into the offline Process Server environment.
    • Create the data stewardship users on the IBM Business Process Manager application server
    • Create authentication aliases for the admin users of InfoSphere MDM on BPM
    • Set the values for the exposed process variables for the Maintenance process application
    • Set the values for the exposed process variables for the Suspected Duplicates process application
    • Set the values for the exposed process variables for the Hybrid MDM Repair Data Quality process application
    • Set the values for the exposed process variables for the Functional Dashboard process application
    • Create the data source for connecting to the MDM database from BPM
    • Configure the login page for IBM Process Portal
    • Add the list of InfoSphere MDM signers to the IBM Business Process Manager application server
    • Restart the IBM Business Process Manager application server
    • Remove the passwords from properties file
  5. If your database server is Microsoft SQL Server or Oracle, a message appears at the end of the installation that there are more steps to complete the installation and configuration.
    Option Description
    Oracle You must run a SQL file against the Oracle database. The SQL file adds the metadata that is required by IBM Stewardship Center. The metadata is necessary for Physical MDM. This metadata is for the process application that is used to resolve suspected duplicate records.
    1. Navigate to the STEWARDSHIP_CENTER_INSTALL_HOME/mdmg/install/sql directory.
    2. Run the following command:
      sqlplus USER_NAME/PASSWORD@ORACLE_DATABASE_NAME MDMBPM_notification_Ora.sql
    3. Restart the IBM WebSphere® Application Server where InfoSphere MDM is deployed to activate the metadata.
    Microsoft SQL Server Although the message indicates that there are more steps, for Microsoft SQL Server there are no additional steps to perform. The installation is complete.
  6. Update the SDPConfigurations exposed process variable (EPV) in the MDM Party Maintenance (MDMPM) process application.
    That EPV identifies the active snapshot for the MDMSDP process application. You can find the active snapshot name of MDMSDP process application in the Process Center console or in Process Designer. By updating the EPV, you ensure that the MDMPM process application interacts correctly with the MDMSDP process application.

    Follow the procedure in Customizing the Physical MDM Suspected Duplicates process application.

Results

Hybrid MDM: The Repair Data Quality process application is installed and configured when you run the primary script file. No further configuration is required for Hybrid MDM unless you need to update the configuration.