After an integration project has been developed and tested, it is necessary to deploy the runtime components to the machines on which they will ultimately run in a production environment. An adapter instance can be deployed, started and managed using TIBCO Administrator from the Administrator web browser.
Using TIBCO Administrator, you can upload the EAR file, deploy the adapter on the machine(s) of your choice, and set runtime options before deployment. Additionally, you can start and stop the adapter using TIBCO Administrator.
A TIBCO administration domain is a collection of users, machines, and components that an administration server manages. There is only one Administration Server for each administration domain. Components within an administration domain can communicate with systems outside of the domain, but the domain is the administrative boundary of your enterprise integration project.
The TIBCO Administrator Server provides a central storage and distribution point for configuration data and schema data needed by an adapter. The server is included in both Administrator editions.
Each administration domain has one and only one TIBCO Administration Server. The TIBCO Administration Server is the machine process that handles the stored project and requests to manage the TIBCO administration domain.
The TIBCO Administrator Server contains its own web server (Apache Tomcat) that can be accessed via the TIBCO Administrator GUI for configuration and monitoring information.
You can access the TIBCO Administration Server using the web-based TIBCO Administrator GUI. The GUI allows you to create users and assign access to projects managed by the Administration Server. You can invoke the GUI from any machine in a TIBCO administration domain.