Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Creating an Instance

Define application instances for every application deployment, after they are created. The processing units defined in the CDD file are bound to a machine (from the machine repository), where the instance runs.

Before you beginNavigate to any of the deployment views for instance management. See Viewing the Instance Management Page for more details.

Procedure
1. In the All Instances page, click Create Instance to create an application instance.
   The PU Instance Creation page is displayed where you can enter details for the instances.
2. Enter the instance details and click Save.

   Processing Unit Instance Properties
   Field | Description
   --- | ---
   Instance Name | The name of the instance
   Processing Unit | Select the processing unit for which you want to create the instance. The dropdown is populated with the processing units defined in the application CDD file.
   Machine Name | Select the machine on which you want to deploy. The dropdown lists all machines registered in the machine repository. See Machine Management.
   BE Home | Select the BE_HOME from list of all the BE_HOME for the selected Machine Name. The list contains all BE_HOME of the BusinessEvents version that matches with the application BusinessEvents version. The BusinessEvents engine is started from the selected BE_HOME.
   JMX Port | The JMX port that is used to communicate with the instance. The JMX port value should not clash with any other port on the machine specified in the Machine Name. The field is auto-filled with an unused port of the machine or existing highest port plus one. For example, if 5501, 5504, and 5506 ports are used then the new port used is 5507. You can change the port number if you do not want to use the suggested port.
   JMX User Name | Optional. Specify the JMX username for user authentication for the JMX connections from the BusinessEvents Enterprise Administrator Agent to the instance. Additional configuration is required to activate the JMX authentication. See Authentication and SSL Configurations for more details.
   JMX Password | Optional. Specify the password for the JMX username specified in the JMX User Name. Additional configuration is required to activate the JMX authentication. See Authentication and SSL Configurations for more details.
   Deployment Path | The file path in the machine where deployed artifacts are stored. The deployment artifacts include the EAR file, the CDD file, the instance specific TRA file, and the batch files to start the instance. The default path is the Default Deployment Path from the associated machine.

   The instance listed under the Instances tab. Also, the instance creation confirmation message is displayed: <Instance Name> instance is created successfully.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.