Creating an Environment

You can create an environment in the ActiveMatrix Administrator UI (with the New Environment wizard ) or CLI.

Prerequisites

Determine whether your environment needs a messaging bus. For more information, see Determining Whether a new Environment should use a Messaging Bus.

GUI

Procedure

  1. Select Infrastructure > Environments.
  2. Click New.
    The New Environment Wizard is displayed.

  3. On the Environment Details page:
    1. In the Name field, type a name for the environment.
    2. Optionally, provide a description and contact information.
    3. To enable security validations, select the Yes check box of Enable Security Validations. When selected, ActiveMatrix Administrator does not allow the following actions:
      • If an environment is not SSL-enabled, you cannot save messaging bus configurations.
      • Creating a node on a host that is not secured with SSL over JMX.
      • Installing a node if the environment's messaging bus configuration is not SSL-enabled.
      • Deploying an application that uses a resource instance that is not SSL-enabled. Resource instances that are referenced by the application's resource instances must also be SSL-enabled. All composite, component, and binding properties are validated.
    4. To automatically deploy applications providing implementation or binding types to the target nodes when deploying user applications that require these applications, select the Yes check box of Enable Auto-Provisioning.
    5. Select the Yes check box of Configure environment without a messaging bus to create an environment that does not use the messaging bus.
      Note: If the environment is being created on an enterprise that does not use a messaging bus, the No Messaging Bus check box is selected and disabled by default and you cannot change the selection.

      For more information on the No Messaging Bus check box, refer to Determining Whether a New Environment should use a Messaging Bus.

  4. Click Next. On the Messaging Bus page:
    • If the enterprise does not use a messaging bus, the messaging bus details are disabled.

    • If the enterprise uses a messaging bus, specify the messaging bus details as required.

      Note: If you type an invalid messaging bus URL in this dialog box and click Finish, the environment is saved but the default messaging bus URL is used (that is, tcp://<hostname>:7222).
  5. Click Finish to create the environment.

CLI

Prerequisites

If you plan to invoke the create target from <TIBCO_HOME>, perform the following steps before you invoke the target.
  • Copy the remote.properties file from <CONFIG_HOME>\admin\enterprise_Name\samples to <TIBCO_HOME>\administrator\<version>\samples.
  • In the <TIBCO_HOME>\administrator\<version>\samples\admin-scripts-base.xml, add the following entry: 
    <property name="tibco.home" location="<location of TIBCO_HOME>" />

Procedure

  1. In the <TIBCO_HOME>\administrator\<version>\samples\environment_build.xml or <CONFIG_HOME>\admin\<Enterprise_Name>\samples\environment_build.xml file, set the action attribute to add and the objectSelector attribute to Environment. 
    target name="create">
   <AMXAdminTask
       remote="true"
       propsFile="${instanceProperties}"
       action="add"
       dataFile="${dataFile}"
       objectSelector="Environment"
       overwrite="true"
       merge="true"
       createIfNotExists="true"
       force="true"
       failOnError="false"/>
</target>
  2. Invoke the create target of the environment_build.xml file.
  3. To create an environment that does not use a messaging bus, in the <TIBCO_HOME>\administrator\<version>\samples\environment_data.xml or <CONFIG_HOME>\admin\<Enterprise_Name>\samples\environment_data.xml file, set the noMessagingBus="true" attribute in the <environment> tag. 
    <Environment xsi:type="amxdata:Environment"
     name="IntegrationEnvironment" description="env_desc" contact="John Smith" autoDeployProductApps="true" noMessagingBus="true">
</Environment>
    Warning: For an existing environment that uses a messaging bus, you cannot set the noMessagingBus attribute.
  4. Invoke the command-line interface on the build file, as described in Invoking the Command Line Interface.

    A sample output for an environment that does not use the messaging bus is shown below. In this example, an environment named NoMessagingBus_Env is created without a messaging bus. 

    create:
 [AMXAdminTask] 13 Apr 2018 17:24:14 INFO - Initializing JSSE's crypto provider class com.sun.net.ssl.internal.ssl.Provider in default mode
 [AMXAdminTask] 13 Apr 2018 17:24:15 INFO - Connecting to AMX Admin server at 'http://admin-server-w530:8120' as user 'root'.
 [AMXAdminTask] 13 Apr 2018 17:24:16 INFO - Executing action 'add' for 1 objects from data file 'c:\amx340\administrator\3.4\samples\environment_data.xml'
 [AMXAdminTask] 13 Apr 2018 17:24:19 INFO - Adding Environment...
 [AMXAdminTask] 13 Apr 2018 17:24:19 INFO - Creating Environment 'NoMessagingBus_Env' without Messaging Bus
 [AMXAdminTask] 13 Apr 2018 17:24:19 INFO - Successfully added Environment 'NoMessagingBus_Env'
 [AMXAdminTask] 13 Apr 2018 17:24:19 INFO - Action finished at 4/13/18 5:24 PM in 0.462 seconds

    See Also: