AIA FP 11.1.1.3 - Deployment Plan Generation for migrating from Dev to Test

Question

Hi All,
Can you please validate the following from a Deployment from Dev to Test perspective. We have almost completed the development for an interface using AIA 11g, and are in the process of moving the interface from one instnace to another, and any help is highly appreciated.
Let us the take Purchase Order Integration between a legacy application and Oracle Purchasing, File Adapter-> Requester ABCS -> EBS -> Provider ABCS -> DB Adapter, which is a classical flow.
1. The Functional person defines a project in the Project Life Cycle Workbench
2. Functional decomposition done through Purchase Prder Business Task, and Service Solution components for each composite in the classical flow
3. The ABCSs are created by linking the corresponding Service Solution Components from the LCW using Service Contructor. These composite.xmls will have the annotation populated by the Service Constructor. It is okay for these composites to have concrete wsdls during development phase, but the concreate ones have to be replaced with abstract ones before geenrating deployment plans.
4. The EBS is not changed, it will have the annotations prepopulated, and there is no need to add any annoations to them
5. The File Adapter and DB Adapters (Transport Adapters?) have to be annotated based on the developer guide
6. The xsds and wsdl go into the mds based using the scripts provided. Any other common components can also be placed into MDS.
7. Once the development is done, Harvest the composites using the AIA Harvester.
8. After harvesting, from the AIA LCW, Generate the BOM. If we harvest all the 5 composites for the Business Task together, and do Generate BOM, does it capture all the composites? Or do they capture only the composites created using the Service Constructor? Or we have to add all the compistes manually to the Business Task?
9. Add Harvested Contents by Editing the BOM -> "Search and Add Existing Composite" option. We couldnt locate the "Add Harvested Composite" option while right clicking the Business Task.
10. Once all the harvested composites have been added to the BOM, export as XML
11. Using the BOM, generate the DeploymentPlan. The deployment plan will have references to the xsds and wsdls in the MDS
12. Using the Deployment Plan and AID, deploy the composites into a new instanec.
These are the questions I have,
1. Is the above understanding correct?
2. Since the MDS is in the Dev database, a pre-requisite for AID seems to be deployment of xsds and wsdls into the Test MDS schema. Can you please validate?
3. What happens to the bpels, xsls, mplans etc? How do they move from one instance to another?
Regards,
Anish

Answer 1

Hi Anish,
Following are the responses -
These are the questions I have,
1. Is the above understanding correct?
1. The Functional person defines a project in the Project Life Cycle Workbench - Yes
2. Functional decomposition done through Purchase Prder Business Task, and Service Solution components for each composite in the classical flow - Yes
3. The ABCSs are created by linking the corresponding Service Solution Components from the PLWB using Service Contructor. These composite.xmls will have the annotation populated by the Service Constructor. It is okay for these composites to have concrete wsdls during development phase, but the concreate ones have to be replaced with abstract ones before geenrating deployment plans.-Yes but location attribute in binding.ws section of composite.xml should always have concrete WSDL location.Use <replaceToken> in DeploymentPlan to replace the ip and port.
4. The EBS is not changed, it will have the annotations prepopulated, and there is no need to add any annoations to them - Yes
5. The File Adapter and DB Adapters (Transport Adapters?) have to be annotated based on the developer guide-Yes
6. The xsds and wsdl go into the mds based using the scripts provided. Any other common components can also be placed into MDS.- Yes
7. Once the development is done, Harvest the composites using the AIA Harvester.-Yes
8. After harvesting, from the AIA PLWB, Generate the BOM. If we harvest all the 5 composites for the Business Task together, and do Generate BOM, does it capture all the composites? Or do they capture only the composites created using the Service Constructor? Or we have to add all the compistes manually to the Business Task?-The 5 composites created by you should have a corresponding service solution component defined.When you define a service solution component in PLWB then a GUID is generated in the database table.You need to retrieve that value and manually enter in the annotation section of composite.xml except for ABCS.Then only the BOM will contain information on all the composites.
9. Add Harvested Contents by Editing the BOM -> "Search and Add Existing Composite" option. We couldnt locate the "Add Harvested Composite" option while right clicking the Business Task.*-Once you harvest it will be visible.*
10. Once all the harvested composites have been added to the BOM, export as XML - Yes
11. Using the BOM, generate the DeploymentPlan. The deployment plan will have references to the xsds and wsdls in the MDS - Yes
12. Using the Deployment Plan and AID, deploy the composites into a new instance.-Yes
2. Since the MDS is in the Dev database, a pre-requisite for AID seems to be deployment of xsds and wsdls into the Test MDS schema. Can you please validate?
Yes the 'UpdateMetaData' section under 'Configurations' in the DeploymentPlan will upload XSDs, WSDLs, DVM,Xrefs into MDS.
3. What happens to the bpels, xsls, mplans etc? How do they move from one instance to another?
The 'Deployments' section will deploy the project into server and write the information into MDS.
Rgds,
Mandrita