Creating an Environment
You can create an environment in the ActiveMatrix Administrator UI (with the New Environment wizard ) or CLI.
Before you begin Determine whether your environment needs a messaging bus. For more information, see
Determining Whether a new Environment should use a Messaging Bus.
GUI
- Procedure
- Select .
- Click
New.
The New Environment Wizard is displayed.
- On the Environment Details page:
- In the Name field, type a name for the environment.
- Optionally, provide a description and contact information.
- To enable security validations, select the
Yes checkbox 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.
- To automatically deploy applications providing implementation or binding types to the target nodes when deploying user applications that require these applications, select the Yes checkbox of Enable Auto-Provisioning.
- Select the
Yes checkbox 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 checkbox is selected and disabled by default and you cannot change the selection.
For more information on the No Messaging Bus checkbox, seeDetermining Whether a New Environment should use a Messaging Bus.
- 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
).
- If the enterprise does not use a messaging bus, the messaging bus details are disabled.
- Click Finish to create the environment.
CLI
Before you begin
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
- 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 toEnvironment
.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>
- Invoke the
create
target of theenvironment_build.xml
file. - To create an environment that does not use a messaging bus, in the
<TIBCO_HOME>\administrator\<version>\samples\
or <CONFIG_HOME>\admin\<Enterprise_Name>\samples\environment_data.xml
environment_data.xml
file, set thenoMessagingBus="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 thenoMessagingBus
attribute. - 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:
- Messaging Bus Configuration of an Enterprise
- Determining Whether an Enterprise Uses a Messaging Bus
- Configuring an Enterprise to Stop Using a Messaging Bus
- Determining Whether a new Environment should use a Messaging Bus
- Determining Whether an Environment Uses a Messaging Bus
- Determining Whether a Node Uses a Messaging Bus
- Determining Whether an Application Uses a Messaging Bus