Showing results for 
Search instead for 
Did you mean: 

how to import all the configuration for the developed adapter

Former Member
0 Kudos

After developed the adapter, there are many steps remains to deploy and use in the XI server.

1)Creating a New Product and Software Component Version in SLD

2)Define the Technical and Business Systems in the SLD

3)Define Business scenarios, design Data types and Message Interfaces and etc in Repository

4)Configuring the Scenario in the Integration Directory

The four steps above are a little complex, I know there are ways to export and import these object seperately, but how could I export all these objects and configurations in these four steps into one package as a whole and import it as a whole too without import one by one?

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hello Mints

Wow - sounds like you've attacked XI from the big end, developing an adapter before doing any XI development!

There is no way to bundle all these things into a single "package", they all have their own mechanisms:

1) Products and Software Component Versions can be exported from the SLD into a zip file which can then be imported into another SLD at your own or a customer site.

2) Technical and Business Systems are specific to an installation or site, so they are never "packaged". They can, however, be "transported" using the SLDs export/import mechanism if you are running a multi-SLD setup within your landscape.

3) Repository objects <i>are</i> meant to be packaged. Use the export functionality in the Integration Builder to create a .tpz file on the XI server that can be moved to another XI repository and imported. Exports can be done at the Software Component Version level (usual for packaging and distribution), the namespace level or for individual objects.

4) Configuration is a per-site activity (see point 2). You might, however, include a Communication Channel Template in your Repository export to help customers configure your adapter.

5?) Don't forget that the adapter must also be deployed using SDM before it can be used!