IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced > Install IBM BPM Advanced > On AIX > Network deployment environment > Configure profiles and create an ND environment > Create or augment ND profiles > DB2 database server > Create or augment dmgr profiles

Augmenting dmgr profiles using manageprofiles.sh

Instead of using PMT, you can use manageprofiles.sh to augment existing WebSphere Application Server V8.0 custom profiles.

Shut down any servers associated with a profile you plan to augment.

Verify that you are not already running manageprofiles.sh on the same profile. If an error message is displayed when you run the command, determine if there is another profile creation or augmentation action in progress. If so, wait until it completes.


Procedure

  1. Determine the template that was used to create the existing profile that you want to augment. You must augment a dmgr profile. You can determine the template by viewing the profile registry in...

      INSTALL_ROOT/properties/profileRegistry.xml

    Do not modify this file; use it only to view the templates.

  2. Find the appropriate template to use for the augmentation.

    Templates for each profile are located in...

      INSTALL_ROOT/profileTemplates/BPM

    ...for BPM templates and under...

      INSTALL_ROOT/profileTemplates

    ...for other products.

    The following templates are available:

    • dmgr.procctr: for a Process Center dmgr profile for IBM BPM Standard.
    • dmgr.procctr.adv: for a Process Center dmgr profile for IBM BPM Advanced.
    • dmgr.procsvr: for a Process Server dmgr profile for IBM BPM Standard.
    • dmgr.procsvr.adv: for a Process Server dmgr profile for IBM BPM Advanced.
    • dmgr.esbserver: for a WebSphere Enterprise Service Bus dmgr profile.

  3. Use the augment parameter to make changes to an existing profile with an augmentation template.

    The augment parameter causes manageprofiles.sh to update or augment the profile identified in the -profileName parameter using the template in the -templatePath parameter. The augmentation templates that you can use are determined by which IBM products and versions are installed in your environment. Verify that you specify the fully qualified file path for -templatePath, because a relative file path for the -templatePath parameter results in the specified profile not being fully augmented.

    Do not manually modify the files that are located in...

      INSTALL_DIR/profileTemplates/BPM

  4. To use the -responseFile parameter, look at the provided sample response files and create a response file that is specific to your environment.

    Ensure that you do not leave blank spaces after the values; for example 'personalCertValidityPeriod=1 ' or 'winserviceCheck=false '. Spaces will cause profile creation to fail.

    The samples are located in the directory...

      INSTALL_ROOT/BPM/samples/manageprofiles

    Choose an appropriate response file based on the database and type of profile (stand-alone or network, Process Center or Process Server). The following sample files are available:

    • PC_Std_DMgr_DB2.response
    • PC_Std_DMgr_DB2zOS.response
    • PC_Std_DMgr_Oracle.response
    • PC_Std_DMgr_SQLServer.response
    • PC_Adv_DMgr_DB2.response
    • PC_Adv_DMgr_DB2zOS.response
    • PC_Adv_DMgr_Oracle.response
    • PC_Adv_DMgr_SQLServer.response
    • PC_Std_Managed_DB2.response
    • PC_Std_Managed_DB2zOS.response
    • PC_Std_Managed_Oracle.response
    • PC_Std_Managed_SQLServer.response
    • PC_Adv_Managed_DB2.response
    • PC_Adv_Managed_DB2zOS.response
    • PC_Adv_Managed_Oracle.response
    • PC_Adv_Managed_SQLServer.response
    • PC_Std_Standalone_DB2.response
    • PC_Std_Standalone_DB2zOS.response
    • PC_Std_Standalone_Oracle.response
    • PC_Std_Standalone_SQLServer.response
    • PC_Adv_Standalone_DB2.response
    • PC_Adv_Standalone_DB2zOS.response
    • PC_Adv_Standalone_Oracle.response
    • PC_Adv_Standalone_SQLServer.response
    • PS_Std_DMgr_DB2.response
    • PS_Std_DMgr_DB2zOS.response
    • PS_Std_DMgr_Oracle.response
    • PS_Std_DMgr_SQLServer.response
    • PS_Adv_DMgr_DB2.response
    • PS_Adv_DMgr_DB2zOS.response
    • PS_Adv_DMgr_Oracle.response
    • PS_Adv_DMgr_SQLServer.response
    • PS_Std_Managed_DB2.response
    • PS_Std_Managed_DB2zOS.response
    • PS_Std_Managed_Oracle.response
    • PS_Std_Managed_SQLServer.response
    • PS_Adv_Managed_DB2.response
    • PS_Adv_Managed_DB2zOS.response
    • PS_Adv_Managed_Oracle.response
    • PS_Adv_Managed_SQLServer.response
    • PS_Std_Standalone_DB2.response
    • PS_Std_Standalone_DB2zOS.response
    • PS_Std_Standalone_Oracle.response
    • PS_Std_Standalone_SQLServer.response
    • PS_Adv_Standalone_DB2.response
    • PS_Adv_Standalone_DB2zOS.response
    • PS_Adv_Standalone_Oracle.response
    • PS_Adv_Standalone_SQLServer.response

    Copy one of the sample response files to your working directory. Use the chmod command to assign the appropriate permissions to your new copy of the response file.

    For example:

    chmod 644 BPM_Dmgr.response

    Edit the parameters in the response file as appropriate to your configuration and save the edited response file. Verify that the templatePath property path matches your specific installation directory.

  5. Run the file from the command line.

    Do not supply a -profilePath parameter.

    For example:

    manageprofiles.sh -augment -templatePath  INSTALL_ROOT/profileTemplates/BPM/dmgr.procctr.adv -profileName MyProfileName

    If you have created a response file, specify the -response parameter without any other parameters.

    For example:

    manageprofiles.sh -response  myResponseFile

    The status is written to the console window when the command is finished running. Normal syntax checking on the response file applies as the file is parsed like any other response file. Individual values in the response file are treated as command-line parameters.


What to do next


Related tasks:
Configuring Business Process Choreographer:
Remove profiles using manageprofiles.sh
Create or augment custom profiles


Related reference:
manageprofiles examples
manageprofiles parameters