EAR file to SDA File conversion is used frequently while developing adapter modules or other NWDS projects for XI / PI which needs to be deployed on PI server.
EAR file to SDA File conversion is used frequently while developing adapter modules or other NWDS projects for XI / PI which needs to be deployed on PI server.
EAR file to SDA File conversion is used frequently while developing adapter modules or other NWDS projects for XI / PI which needs to be deployed on PI server.
EAR file to SDA File conversion is used frequently while developing adapter modules or other NWDS projects for XI / PI which needs to be deployed on PI server.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online from Scribd
Download as pdf or txt
You are on page 1/ 10
How to Convert EAR to SDA File
Applies to: SAP Net Weaver Process Integration 7.1 or 7.0. For more information, visit the Service Bus-based Integration homepage. This document caters to the needs of those XI/PI developers/consultants who are using module development etc. in which EAR to SDA file conversion are required
Summary EAR file to SDA file conversion is used frequently while developing adapter modules or other NWDS projects for XI/PI which needs to be deployed on PI server.
Authors:
Mayank Gupta, Neelansha Singh
Company: Infosys Technologies Limited
Created on: 21 September 2010
Author Bio Mayank Gupta is working as a Senior Systems Engineer on SAP XI/PI with Infosys Technologies Limited. He began his career in Nov-2007 and since then he has been working on SAP XI/PI. His area of expertise is SAP XI/PI.
Neelansha Singh is working as a Senior Systems Engineer on SAP XI/PI with Infosys Technologies Limited. She began her career in Nov-2007 and since then she has been working on SAP XI/PI. Her area of expertise is SAP XI/PI.
Introduction In PI, whenever we develop a custom adaptor module, java proxy or we want to deploy external JDBC/JMS drivers to the server, we need SDA (Software Delivery Archive) file to be deployed on PI Server using JSPM (Java Support Package Manager) in PI 7.1 and using SDM(software deployment manager) in older versions. In this document conversion of EAR file (created using NWDS or any IDE) to SDA file has been explained. JSPM (Java Support Package Manager) Custom Adapter Module Java Proxy External Driver Configuration in Process Integration 7.1 Using JSPM
Prerequisites Net weaver Developer Studio (NWDS) 7.1 should be installed on the local system.
Converting EAR to SDA and Deploying it using JSPM
Convert EAR to SDA Step 1: Export EAR project onto the local system. Right click on EAR Project, select Export and then select SAP EAR file.
Fig. 01
Step 2: Delete all SAP specific jar files from the EAR file by unzipping the .ear file and then again zip the files. SAP jar files are deleted because all these files are already available on PI server and the references to them have been given in application-j2ee-engine.xml file.
Step 3: Using nwcetool (or CECTL i.e. Composition Environment Command Line Tool) provided with NWDS 7.1, convert .ear file to .sda file. Use createsda command and command prompt to create the SDA file.
CECLT.pdf
Documentation for using this tool is available on NWDS installed location.
Step 4: Run Command Prompt and go to the nwcetool location and run the file nwcetool.bat to start nwcetool.
Step 5: Execute the createsda command to convert .ear to .sda file. Syntax for createsda:createsda n <application name/ JNDI Name> v <Vendor name> l <application name/ JNDI Name> c 2 type J2EE <source file location> <Target file location> createsda n ExcelAdapter v pi.adapter.poc l ExcelAdapter c 2 type J2EE C:\EAR_ExcelAdapter.ear c:\result16\SDA_ExcelAdapter
Fig. 02 Application Name Should not be more than 20 characters!!!! createsda n ExcelPOCAdapter123456 v pi.adapter.poc l ExcelPOCAdapter123456 c 2 type J2EE C:\AdapterExcelEAR.ear c:\result15\SDA_AdapterExcel1
Fig. 04 Step 7: Now SDA file is ready to be deployed. Deploy it using JSPM. Deploy using JSPM: Refer to Section 1.3 of document: External Driver Configuration in Process Integration 7.1 Using JSPM
Step 1: After Deploying the SDA file, the logs for our module deployment (SDA file) can be seen to check if it is deployed properly or not. The logs can be seen both from the current logon session and from previous sessions. Logs from every session are written to a subdirectory whose name contains the time stamp of the session. Logs are stored at /usr/sap/<SID>/<Instance name>/j2ee/JSPM/log directory Step 2: Success or failure of EJB module deployment can be checked in NWA (Net Weaver Administrator):JNDI Browser -> EJB_AdapterModule
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.
