Configuring an application-based endpoint – Acoustic Help Center

Encourage adoption and use of your product or business solution by making it available to Acoustic Exchange users as a Acoustic Exchange endpoint. You must complete a design and approval process in order to be an endpoint.

In Acoustic Exchange, an endpoint represents a product or business solution that is part of the Acoustic Exchange Partner ecosystem. Acoustic Exchange provides marketers with new ways to match and combine the capabilities and outputs of these products to solve business problems. As a result, appearing as an endpoint in Acoustic Exchange increases a product's value to a marketer.

To use a product from the Acoustic Exchange Partner ecosystem in their Acoustic Exchange user account, marketers must register the product as an endpoint in their account. To be able to register a product as an endpoint, Acoustic Exchange users must have an open account or valid license to the product and be able to provide valid access credentials. This is how Acoustic Exchange encourages marketers to patronize members of the Acoustic Exchange Partner ecosystem.

In Acoustic Exchange, endpoints are based on a set of metadata that is referred to as a Acoustic Exchange application. An application serves as a blueprint that defines how your product or solution appears in Acoustic Exchange, what it provides or accepts, and the authentication that it requires to interact with Acoustic Exchange.

To help build your application, you can use the Integration Manager. The Integration Manager provides a single, intuitive interface to define your data syndications and data center deployments, and also guides you through testing, validation, and promotion as a publicly available Acoustic Exchange endpoint.

The initial partner provisioning and application design takes place in the Acoustic Exchange Pilot environment. When your application is ready to go to market and IBM approves your solution for Acoustic Exchange, your application can move to the Production environment so that it is available to Acoustic Exchange users.


Edit	During the initial edit phase, you specify the types of data that your endpoint produces or consumes, how to connect to your business systems, and how Acoustic Exchange users can submit their credentials through Acoustic Exchange.
Implement	During the implementation phase, you implement APIs that enable your product or solution to communicate with Acoustic Exchange. The design of your application determines the APIs that you need.
Test	In the test phase, you can perform the same tasks that Acoustic Exchange users perform when they attempt to register your endpoint for their account. Acoustic Exchange provides the Acoustic Exchange Test Drive as an interactive tool to test and refine your designs.
Validate	During the application validation phase, you demonstrate how the application works. You can move to the final phase only after Acoustic approves your application.
Promote	The promote phase determines when your application goes live in the Acoustic Exchange Production environment. When your application goes live in Production, your endpoint appears to users on the Acoustic Exchange Endpoints tab. You decide when to promote your application to Production.

Endpoints