There's nothing special when building an adaptermodule in a track. You only have to make sure to put all required XI jars into an External Library DC in order to be able to compile your EAR and EJB Module DCs.
I have a more precise question. If we use a track to develop an adaptermodule, do we need to use the SDM to deploy it after or is it done automatically ? With a track, a development configuration is used. What does this development configuration allow to me ?
While using track based development, SDM is not required to be handled manually for deployment. Automatic deployment takes place when the option 'Disable automatic deployment' is not selected for the runtime systems 'Dev' and 'Cons' in the CMS->Landscape Configurator->Runtime Systems tab. For the 'Test' and 'Production' automatic deployment takes place.
For knowing the purpose and advantages of Development Configurations, go through
but how does it work ? When we are in the Developer Studio, i guess there is an option to 'deploy'. And then what happens ? The adapter module goes to Dev, Test and Production or is there anything to do ?
The External Library DC containing the jar files is declared as public part and made use of as 'Used DC' in the project. The activity(ies) created while creating the DCs must be available in the 'Open Activity'. Once the DC build goes successful, then you can check-in those open activities. Subsequently the activities are activated (deployed) in the central development system. After activation, you will see them in the 'Transport View', where you can release them. Here ends the task of developer.
On releasing, they will be queued up in the Cons stage of CMS and ready for import. After assembly, they will be imported into Test and Prd systems. These actions are taken care by CMS administrator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.