Copyright © Cloud Software Group, Inc. All Rights Reserved

Deploying TIBCO API Exchange Gateway Processing Units

The full deployment of API Exchange Gateway contains the deployment of following components, which can be done on a single server or can be distributed across multiple servers.

−	Core Engine

−	Central Logger

−	Global Throttle Manager

−	Cache Manager (Optional)

−	Cache Cleanup Agent (Optional)

See High Availability Deployment Of Runtime Components for deployment details of runtime components.

Requirements For Deployment

TIBCO API Exchange Gateway software packages the required files for deployment of its engine and other processing units, by default. Typically, a deployment requires one or more Enterprise Archive (EAR) files and one or more Cluster Deployment Descriptor (CDD) files. You must ensure the third party jars are available at runtime, if applicable.

In case, if any customizations are made in the ASG_DefaultImplementation project of the gateway, you will need to configure the CDD file settings and build the EAR file.

Deployment Options

You can deploy the Core Engine and the other processing units in the following ways:

•	Using TIBCO API Exchange Gateway Monitoring and Management Server. This is the recommended way. See Deploy Using Monitoring And Management Server.

•	Run the Core Engine and run time components at the command-line. See Running Processing Units At Command Line.

Copyright © Cloud Software Group, Inc. All Rights Reserved