A deployment in Acoustic Exchange defines where and how to access the software that supports the product or solution that is provided by the Acoustic Exchange partner and that is represented by a Acoustic Exchange endpoint.
Acoustic Exchange applications are not software that is hosted by Acoustic Exchange. Business solutions that are represented in Acoustic Exchange as endpoints are actually hosted on servers and data centers outside of Acoustic Exchange. To enable Acoustic Exchange to connect to endpoints automatically, you must define how and where you have deployed the software that provides or receives data that passes through Acoustic Exchange.
Acoustic Exchange can connect to endpoints that are deployed on multiple servers or data centers. You must define each deployment separately.
You must define a unique deployment ID and a name for the deployment.
Depending on the types of data that you plan to exchange, you must provide the specific URLs to where to find or deliver the data. The Integration Manager displays fields to enter source and destination URLs based on the data syndication choices that you make in the Specify syndication types section.
Default deployment in te Integration Manager
By default, the Integration Manager defines a single deployment in every new application. You can use this default deployment if your product or solution is deployed on a single data center.
If your product or solution is deployed on multiple data centers, you must define additional deployments.
If your product or solution is installed on a local network, you do not need to define a deployment. This type of product deployment is sometimes called an On Prem installation.
The default deployment is provisioned to use the Instructions only endpoint registration method. You can change the registration method to Direct connect when you specify the provisioning method for the application.