Installing business process applications, using the administrative commands

Why and when to perform this task

Note the title of this topic has changed - was Installing BPEL process applications that WebSphere Studio did not generate.You can use WebSphere Integration Developer to model business processes and then generate application modules from the process models. You can then use the administrative console to install these applications in Business Process Choreographer.

Business Process Choreographer also supports BPEL-based processes that WebSphere Integration Developer did not generate. You must map these process applications to constructs that can be used directly by Business Process Choreographer. A script is provided for you to specify options for creating and installing the application. The command-line parameters define application-specific parameters, for example, whether database tables are created automatically. You can provide an options file to use with the script to specify options for deploying the individual processes in the application.

Steps for this task

  1. Change to the Business Process Choreographer directory utilities directory. On Windows platforms, enter:
    cd install_root\ProcessChoreographer\util
    On z/OS, UNIX and Linux platforms, enter:
    cd install_root/ProcessChoreographer/util
  2. Run the deploy script. On Windows platforms, enter:
    install_root\bin\wsadmin -f deployBPEL.jacl [options]
    On UNIX platforms and z/OS, enter:
    install_root/bin/wsadmin -f deployBPEL.jacl [options]
    Parameter Description Value range Default
    Options for creating EAR files
    -scrdir Source directory that contains the BPEL processs definitions and the associated WSDL and XSD definitions. (directory) "." (period)
    -options BPEL partner link to WSDL port binding table and process deployment settings. (file name ) (none)
    -earFileName Fully-qualified or relative file name of the output EAR file. (file name: *.ear)  
    Options for installing applications in Business Process Choreographer
    -activateProcess Install application in WebSphere Application Server. Yes or No Yes
    -createTables Automatically create container-managed persistence (CMP) tables for interruptible processes. Yes or No

    If the database system is DB2 UDB OS/390 Version 7, the only allowed value is No.

    Yes
    -database Type of database.

    DB2UDB_V81
    CLOUDSCAPE_V5
    DB2UDBOS390_V7
    DB2UDBISERIES
    INFORMIX_V93
    MSSQLSERVER_2000
    ORACLE_V8
    ORACLE_V9I
    SYBASEV1200
    SYBASEV1250

    DB2UDB_V81
    -target Name of the WebSphere deployment target. server, node, or cluster name Not needed for a single server.
    Binding parameters for the application
    -genericMdbConnection Factory name Global Java Naming and Directory Interface (JNDI) name of the generic Business Process Choreographer MDB queue connection factory.   jms/BPECF
    -genericMdbQueue name Global JNDI name of the generic Business Process Choreographer MDB queue.   jms/BPEIntQueue
    -jndiInitialContextFactory name Initial context factory.   com.ibm.websphere.naming. WsnInitialContextFactory
    -jndiProviderURL url JNDI provider URL   If you do not specify a value, the server-supplied value is used.
    To generate a process application EAR file, for example, enter:
    wsadmin -conntype NONE 
            -f install_root/ProcessChoreographer/util/deployBPEL.jacl 
            -srcdir <mySamples>\SimpleProcess
            -earFileName SimpleProcess.ear 
            -options interfaces4Partner.opt
            -activateProcess No
    For this example, the interfaces4Partner.opt options file might look like this:
    *.deployAsEJB=Yes
    To generate and install a process application, for example, enter:
    wsadmin -f install_root/ProcessChoreographer/util/deployBPEL.jacl 
            -srcdir <mySamples>\SimpleProcess
            -earFileName SimpleProcess.ear 
            -options interfaces4Partner.opt
            -database CLOUDSCAPE_V5
    The interfaces4Partner.opt options file is the same as in the previous example.

Result

If you create a process, you can use the administrative console to install and manage the process. If you create and install the process, you can use the administrative console to manage the process template instances.

Related information
Options file for deployBPEL.jacl script


Copyright IBM Corp. 2003, 2005