Copyright © Cloud Software Group, Inc. All Rights Reserved

Edit Application Configuration Dialog

Fields can be edited if this dialog is invoked from the Configuration Builder pane. If invoked from the Deployed Configuration pane, the fields are read only.

The following tabs are available:

•	General Tab

•	Advanced Tab

General Tab

Application Archive

Provides information about the enterprise archive file including the package name, version, description, creation date and owner.

Upload New EAR File

Allows you to replace the current enterprise archive file with an updated version.

Application Parameters

Provides information about the application name, associated deployment name, description and contact name for the application.

Advanced Tab

The Reset to Defaults button resets all global variables to default settings as set in the enterprise archive file.

Global Variables

Displays the global variables set in the enterprise archive file for this application. The following global variables are predefined by default:

•	DirLedger — Used by the system when defining the path name of the TIBCO Rendezvous certified messaging ledger file. The default is the root installation directory.

•	DirTrace — Used by the system to partially create the path name for log file used by the adapter. The default is the root installation directory.

•	HawkEnabled — Used by the system to indicate whether TIBCO Hawk is used to monitor the adapter. True indicates that a Hawk microagent is defined for the adapter. False indicates the microagent is not to be used. Default is False.

•	JmsProviderUrl — A JMS provider URL tells applications where the JMS daemon is located. Setting this value mostly makes sense in early stages of a project, when only one JMS daemon is used.

•	JmsSslProviderUrl — Specifies where the JMS server, running in the SSL mode, is located. Setting this value mostly makes sense in the early stages of a project, when only one JMS server is used.

•	RemoteRvDaemon — Used by the system to identify the TIBCO Rendezvous routing daemon. See TIBCO Rendezvous Administration for details about specifying the routing daemon name.

•

RvDaemon — Used by the system to identify the TIBCO Rendezvous daemon parameter. The parameter instructs the transport object about how and where to find the Rendezvous daemon and establish communication. The default value is 7500, which is the default value used by the Rendezvous daemon. See TIBCO Rendezvous Concepts for details about specifying the daemon parameter.

•

RvNetwork — Used by the system to identify the TIBCO Rendezvous network parameter. Every network transport communicates with other transports over a single network interface. On computers with more than one network interface, the network parameter instructs the TIBCO Rendezvous daemon to use a particular network for all outbound messages from this transport. See TIBCO Rendezvous Concepts for details about specifying the network parameter.

•

RvService — Used by the system to identify the TIBCO Rendezvous service parameter. The Rendezvous daemon divides the network into logical partitions. Each transport communicates on a single service; a transport can communicate only with other transports on the same service. See TIBCO Rendezvous Concepts for details about specifying the service parameter. Default is 7500

•	RvaHost — Used by the system to identify the computer on which the TIBCO Rendezvous agent runs. See TIBCO Rendezvous Administration for details about specifying the rva parameters.

•	RvaPort — Used by the system to identify the TIBCO Rendezvous agent TCP port where the agent listens for client connection requests. See TIBCO Rendezvous Administration for details about specifying the rva parameters. Default is to 7501.

•	TIBHawkDaemon — Used by the system to identify the TIBCO Hawk daemon parameter. See the TIBCO Hawk Installation and Configuration manual for details about this parameter. Default is the value that was set during domain creation (7474 by default).

•	TIBHawkNetwork — Used by the system to identify the TIBCO Hawk network parameter. See the TIBCO Hawk Installation and Configuration manual for details about this parameter. Default is an empty string.

•	TIBHawkService — Used by the system to identify the TIBCO service parameter. See the TIBCO Hawk Installation and Configuration manual for details about this parameter. Default is 7474.

•

MessageEncoding — The message encoding set for the application. The default value is ISO8859-1, which only supports English and other western European languages that belong to ISO Latin-1 character set. After the project is deployed in an administration domain, the messaging encoding set at design time is overridden by the domain's encoding property. All the TIBCO components working in the same domain must always use the same encoding for intercommunication. See TIBCO Administrator Server Configuration Guide for more information.

TIBCO ActiveMatrix BusinessWorks Deployment Repository Instance

When TIBCO Administrator deploys an application, it creates an application repository which contains information about the application configuration. You can view and change certain aspects of the application repository.

In Transport you select the transport the administration server uses to communicate with the client application. Choose local, rv (TIBCO Rendezvous) or HTTP, or HTTPS if the administration domain has been set up to use HTTPS.

•	local. By default, the transport is set to local. This means that the application repository will be sent to the target machine. This allows the application to run independently of the administration server.

If you change the transport from local to another value, the application repository will not be pushed to the target machine, and the application will communicate with the administration server at runtime.

For more information about these choices, see TIBCO Administrator Server Configuration Guide.

The local choice is supported only if the target machines have installed TIBCO Runtime Agent 5.9.0 or later.

•	rv. If selected, the client application will use TIBCO Rendezvous to communicate with the administration server. The following fields become available:

−	Server Name — administration server name.

−	Instance Name — Service instance name, that is, the instance of the service running on a particular machine.

−	User Name — User authorized for this application repository. Defaults to the user currently logged into Administrator.

−	Password — User’s password.

−	Timeout — Amount of time in seconds allowed for completing a task, such as retrieving information from the server. Defaults to 600 seconds.

−	Service, Network, Daemon — TIBCO Rendezvous connection parameters used.

−	Discovery Timeout — Amount of time in seconds allowed for the initial connection to the administration server.

−	Regional Subject — TIBCO Rendezvous subject prefix used for regional read-operation in the load balancing mode. For additional information see TIBCO Administrator Server Configuration Guide.

−	Operation Retry — Number of times to retry after a timeout occurs.

•	http. If selected, the client application will use HTTP to communicate with the administration server.

If your administration domain is not initially enabled for HTTPS, and there are deployed applications in the domain that use HTTP to connect to the application repository, the service instances will not restart after they are shut down. In this case, you must redeploy each service instance after changing the transport to HTTPS.

−	Server Name — administration server name.

−	Instance Name — Service instance name, that is, the instance of the service running on a particular machine.

−	User Name — User authorized for this application repository. Defaults to the user currently logged into Administrator.

−	Password — User’s password.

−	Timeout — Amount of time in seconds allowed for completing a task, such as retrieving information from the server. Defaults to 600 seconds.

−	HTTP URL, HTTPS URL — The URL on which the client attempts to connect to the server. What displays depends on whether you configured the server for HTTPS.

Note: You cannot use HTTP or HTTPS to connect to a 4.x adapter.

Preview URL

If you have selected, rv or http in the Transport field, click the preview URL to display the URL that the application uses to access the application repository.

Copyright © Cloud Software Group, Inc. All Rights Reserved