Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Applications : Creating an Application

Creating an Application
GUI
About this task 
The New Application wizard allows you to create an application, specify its distribution, configure properties, substitution variables, features, wire services and references, and create bindings.
Procedure 
1.
Click the Applications tab.
2.
Click New New Application.
The New Application wizard displays.
3.
1.
2.
* EAR files created using a newer version of the adapter palette should not be deployed in environments where an older version of the adapter is deployed.
1.
4.
Application names cannot contain the characters \, /, :, *, ?, ", <, >,|, whitespace, %, #, &, (, ), or comma and they cannot be the same as the node name.
Application Folder - accept the default location or click Select... to choose a folder for the application.
Click Next.
5.
The feature is not re-imported if it exists in Administrator.
Click Next.
6.
The number of applications deployed on each node are displayed. This helps in distributing your applications across the available nodes.
If you have multiple nodes running you can choose to deploy the application to more than one node by checking the checkbox for Advanced to fine tune the distribution.
Select nodes for an item - choose items from the composite tree on the left and drag to nodes on the right. Double-click the items to distribute it to all the nodes.
Components or bindings in logical nodes will not appear in the item lists as they can not be distributed separately from the logical node.
Distribution is cumulative. So if a component is explicitly distributed to node A and the application is distributed to node B, then the component will be distributed to both nodes A and B during deployment.
Click the link to see all the nodes to which it is distributed.
Select items for a node - choose a node from the list on the left and drop on items on the right. Double-click a node to distribute all items to the selected node.
Click the link under a node name to see all the fragments of the application distributed to the node.
Click the Clear distribution for the selected items button to delete the distribution.
Click Next.
7.
Choose a version from the Software dropdown list and click Next.
8.
If the references have been configured at design time, the references with the wiring is displayed.
The Edit Binding dialog displays. Edit the configuration information and click Save.
If the references have not been configured at design time, choose one of the following options:
The Add Binding dialog displays. Edit the configuration information and click Save.
To wire to a target service, click Wire to a target service.
The Target Service dialog displays. Choose a listed service and click Save.
Click Next.
9.
To import the resource template check the checkbox for that resource template and click Next.
10.
Expand the tree for Owner to view and edit the displayed properties. When you click on a cell in the Property Value column, a picker icon appears that allows you to select existing resource instances of the correct type.
Click Next.
11.
In the Local Value column, edit application and application fragment substitution variable values. When you click on a cell in the value column, a picker icon appears that allows you to select existing resource instances of the correct type.
Click Add to create additional substitution variables.
Make sure the value of the HawkEnabled property is set to true.
Click Next to continue.
12.
13.
Back - navigate to any previous screen in the wizard.
Deploy - deploys the newly created application.
Save and Exit - saves the setup information and exits the wizard.
The application is added to Applications list. You must manually specify the application's distribution in the Distribution tab below the Applications list and manually configure any properties, bindings or substitution variables.
Cancel - does not create the application. Any DAA uploaded or resource templates imported in previous steps will remain.
Result 
Only the adapter components contained in the EAR file are displayed in the Administrator UI.
CLI
Before you begin 
The application template and environment must already exist in the enterprise.
Procedure 
1.
2.
In the build file set the action attribute of the AMXAdminTask element to add and the objectSelector attribute to Environment/Application.
<AMXAdminTask action="add" objectSelector="Environment/Application" />
3.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved