Getting Started

Starting bcappmanage

To start the bcappmanage utility, change to the directory BC_HOME/tools/bcappmanage, and type the following

bcappmanage

See the section Online Help for information about using online help.

Once the TIBCO BusinessConnect application has been configured and deployed, you can quickly export the existing configuration and deployment repositories.

After these preparation tasks are done, continue by re-installing the application, importing the previously exported configuration, creating tables (if needed), and deploying and managing the application using the command line interface.

To configure and deploy the BusinessConnect application with TIBCO BusinessConnect Scripting Deployment, the sequence explained in Managing Applications Using bcappmanage must be followed.

Users who are planning to use the Oracle OCI drivers must specify the Oracle Client Library path in the environment variable

tibco.env.ORACLE_CLIENT_PATH of the file bcappmanage.tra located under BC_HOME/tools/bcappmanage.

The value should point to the Oracle native client libraries directory.

• On Windows, this is typically ORACLE_CLIENT_HOME/BIN directory; for example C:\oracle\product\10.2.0\client\BIN.

• On UNIX systems, this is typically the ORACLE_CLIENT_HOME/lib or

ORACLE_CLIENT_HOME/lib32 directory.

Managing Applications Using bcappmanage

|

Managing Applications Using bcappmanage

TIBCO BusinessConnect Scripting Deployment cannot be used for the initial TIBCO BusinessConnect application installation and configuration, which must be performed in the TIBCO BusinessConnect GUI using TIBCO Administrator.

After you have used the GUI interface to install and configure the application, you can use either the same GUI or the command line interface to perform management and deployment tasks. Before performing any of the listed tasks, make sure to first provide information for the file commonConfig.properties. More details about this configuration file are available in Chapter 3, Parameters for commonConfig.properties.

All parameters in the file commonConfig.properties will be validated by TIBCO Runtime Agent. If any of the required parameters are missing or have been entered in a format that is not acceptable, TIBCO Runtime Agent will throw an error or insert default values, where appropriate.

To see the completed file commonConfig.properties with added parameters, see Appendix B, Configuration Properties File.

Task A: Preparing for Deployment

To prepare for configuration of a TIBCO BusinessConnect application using TIBCO BusinessConnect Scripting Deployment, the deployment configuration and configuration repository need to be exported. Both tasks are required and can be done in any order.

1. Export Deployment Configuration bcappmanage -exportDeployConfig

The generated XML file will be used during the task invoked by the command

-importDeployConfig. Repeat the command -exportDeployConfig if any of the configured deployment parameters have changed.

The complete command reference is available in -exportDeployConfig. 2. Export Configuration Repository

bcappmanage -exportConfigRepo

This task is used for generating CSX configuration export files from the BusinessConnect configuration repository. It supports four main categories:

participants, operations, certificates, and entire installation.

The complete command reference is available in -exportConfigRepo.

12

|

Task B: Deploying and Managing TIBCO BusinessConnect Applications

Once the configuration repository and the deployment configuration are exported for the selected application categories, you can install, deploy, and manage the TIBCO BusinessConnect application.

1. Create Installation

bcappmanage -createInstallation

Same as the Create Installation task in the TIBCO BusinessConnect GUI, this task creates the TIBCO BusinessConnect installation. The complete command reference is available in -createInstallation.

2. Activate Protocol

bcappmanage -activateProtocol

This task allows activation in one pass for all available protocol plugins installed on the machine where bcappmanage is running. The complete command reference is available in -activateProtocol.

3. Create Tables (optional) bcappmanage -createTables

This task is optional and is not needed when the audit, non-repudiation, and runtime data will be stored in the database account that is the same as the account of the configuration store. The complete command reference is available in -createTables.

4. Import Configuration Repository bcappmanage -importConfigRepo

Imports the previously exported configuration repository saved as a CSX file.

The complete command reference is available in -importConfigRepo. 5. Create Application

bcappmanage -createApp

Creates deployment configuration for a BusinessConnect application service.

The complete command reference is available in ^-createApp. 6. Import Deployment Configuration

bcappmanage -importDeployConfig

Imports the previously exported deployment configuration in XML format and also does machine assignments. Names of the Interior hosts in the

commonConfig.properties file must be specified exactly as they are shown on the screen Resource Management>Machines in TIBCO Administrator.

Same needs to be ensured for all property settings that use the machine names

Managing Applications Using bcappmanage

|

7. Configure FT Cluster Map (optional) bcappmanage -configFTClusterMap

This command is optional. It configures mappings of machines to

fault-tolerant groups and mappings of fault-tolerant groups to Public Smart Routing clusters.

Configuration of fault-tolerant clusters for Public Smart Routing with TIBCO BusinessConnect Scripting Deployment requires the machine bindings of service instances be configured during the –importDeployConfig task. This tool does not recognize machine bindings that are configured using the BusinessConnect administration console GUI. The complete command reference is available in -configFTClusterMap.

8. Deploy Application

bcappmanage -deployApp

This command corresponds to the Deploy task in the TIBCO BusinessConnect GUI and deploys the BusinessConnect application service with an option to suspend starting of all service instances on deploy. The complete command reference is available in ^-deployApp.

9. Start Application

bcappmanage -startApp

This task can be used for starting the BusinessConnect engines deployed in scripted mode. The options define whether an individual engine or all engines will be started, and also whether these engines are on the Interior server. The complete command reference is available in -startApp.

Task C: Prepare and Manage Gateway Server Tokens

Once the Interior Server is deployed and running, you can create the Gateway Server token and use it to start and deploy the Gateway Server. Two commands for managing these tokens have been supplied:

• -createGatewayToken.

• -listGatewayToken.

Other Management Tasks

These tasks are dedicated to managing configured and deployed applications:

• Undeploy Application, which is presented in -undeployApp.

• Delete Application, which is presented in -deleteApp.

• Stop Application, which is presented in ^-stopApp.

• Kill Application, which is presented in -killApp.

14

|

|

Chapter 3 Parameters for commonConfig.properties

This chapter explains the parameters that are contained in the file

commonConfig.properties.

Topics

• Overview, page 16

• JDBC Maps, page 17

• Binding Maps, page 18

• Cluster/FT Map, page 22