When TIBCO Administrator deploys an application, it creates an application repository which contains information about the application configuration.
We can view and change certain aspects of the application repository.
We can view and change certain aspects of the application repository.
TIBCO Admin -Transport options local / rv / http
In TIBCO Admin , browse new ear file and go to the path "Edit Application Configuration > Advanced tab"
There are two sections
Global Variables
TIBCO BusinessWorks and Adapters Deployment Repository Instance
under the section "TIBCO BusinessWorks and Adapters Deployment Repository Instance" there is Transport drop down box having the options local ,rv and http
This transport is that the administration server uses to communicate with the client application.
In TIBCO Admin , browse new ear file and go to the path "Edit Application Configuration > Advanced tab"
There are two sections
Global Variables
TIBCO BusinessWorks and Adapters Deployment Repository Instance
under the section "TIBCO BusinessWorks and Adapters Deployment Repository Instance" there is Transport drop down box having the options local ,rv and http
This transport is that the administration server uses to communicate with the client application.
- 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.
The local choice is supported only if the target machines have installed TIBCO Runtime Agent 5.3 or later.
- rv
If rv selected, the client application will use TIBCO Rendezvous to communicate with the administration server.
- http
If selected, the client application will use HTTP to communicate with the administration server.
If 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.
If 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.
The parameter HTTP URL, HTTPS URL is the URL on which the client attempts to connect to the server. What displays depends on whether you configured the server for HTTPS
