Transport of XML Configuration 

Procedure

There are two ways to transport the XML configuration to the UWL via UWL Deployment Hook.

Offline Deployment

You can transport the XML configuration to the UWL via offline deployment:

       1.      Create the zip file for your XML configuration (see Internationalization of XML Configuration).

For example, uwl_sample.zip. If no internationalization is needed then instead of uwl_sample.zip an XML file itself can be used, but it also has to start with uwl_, for example uwl_sample.xml.

       2.      Put it in the sda file. In the following example the configuration is sample, and the project is com.sap.xyz.sample. The sda file also contains:

META-INF\MANIFEST.MF

META-INF\SAP_MANIFEST.MF

META-INF\com.sap.xyz.sample-dd.xml

Where MANIFEST.MF:

Manifest version: 1.0

Specification version: 1.0

 

SAP_MANIFEST.MF:

Manifest-Version: 1.0

Software type: FS

Deploy file: com.sap.xyz.sample-dd.xml

Key name: com.sap.xyz

Key vendor: sap.com

Key location: SAP AG

Key counter: 7.0009.20061707180224.0000

 

com.sap.xyz.sample-dd.xml:

<?xml version="1.0" ?> <SDA name="com.sap.xyz.sda">    <SoftwareType>FS</SoftwareType>    <fs-deployment-descriptor version="1.0">    <fileset id="com.sap.xyz">    <display-name>test</display-name>    <description>test</description>    <default-deployment-dir>${com.sap.systemdir}/config/cm/etc/uwl      </default-deployment-dir>    </fileset>    </fs-deployment-descriptor> </SDA>

 

After the sda is deployed, upon starting the UWL service it uploads the XML configuration file  and registers it with the medium priority.

Additional Mechanism of Automatic Deployment

An SDA can deploy UWL configuration files into KM folder /etc/uwl and the UWL reads them during the UWL start-up.

It is up to you how you produce this SDA, e. g. Japro, NWDI. Since the deployment type has to be changed from J2EE to FileSystem the key name in SAP_MANIFEST.MFshould be changed.  For Japro build, the key name is the same as <title> in the BeginPackSDA macro (<name>, <deploy file>, <specification name>, <specification version>, <title>[,<techno dir>]).

Following is how the SDA deployment descriptor looks like:

<SDA name="com.sap.erp.ess">    <SoftwareType>FS</SoftwareType>    <fs-deployment-descriptor version="1.0">    <display-name>ERP Sda for UWL</display-name>       <fileset id="ERP ESS">       <display-name>ERP Ess</display-name>       <description>ERP ESS</description>       <default-deployment-dir>${com.sap.systemdir}/config/cm/etc/uwl              </default-deployment-dir>       </fileset>    </fs-deployment-descriptor> </SDA>

Online Deployment

You can transport the XML configuration to the UWL via online deployment:

       1.      Create the zip file for your XML configuration (see Internationalization of XML Configuration).

For example, uwl_sample.zip. If no internationalization is needed then instead of uwl_sample.zip an XML file itself can be used, but it also has to start with uwl_, for example uwl_sample.xml.

       3.      Put it in the par file in the format as shown in the following example.

In the example the configuration is sample, and the project is com.sap.xyz.sample.

PORTAL-INF\private\classes\uwl_sample.zip

PORTAL-INF\portalapp.xml

Where portalapp.xml:

<?xml version="1.0" encoding="iso-8859-1"?> <application name="com.sap.xyz.sample" alias="com.sap.xyz.sample">         <application-config>                 <property name="releasable" value="true"/>                 <property name="PreservedConfigPaths" value=""/>                 <property name="Vendor" value="sap.com"/>                 <property name="ServicesReference" value="com.sap.netweaver.bc.uwl"/>         </application-config>         <components/>         <services/> </application>

       4.      Put the par file into an ear file. The ear file also contains the following:

META-INF\MANIFEST.MF

META-INF\SAP_MANIFEST.MF

META-INF\application-j2ee-engine.xml

META-INF\application.xml

META-INF\com.sap.xyz.sample-dd.xml

Where MANIFEST.MF:

Manifest-Version: 1.0

Specification-Version: 1.0

 

SAP_MANIFEST.MF:

Manifest-Version: 1.0

Software type: J2EE

Deploy file: com.sap.xyz.sample-dd.xml

Key name: com.sap.xyz.sample

Key vendor: sap.com

Key location: SAP AG

Key counter: 7.10.20061707170244.0000

 

application-j2ee-engine.xml:

<?xml version="1.0" encoding="UTF-8" ?> <application-j2ee-engine>    <modules-additional>       <module>          <entry-name>com.sap.xyz.sample.par</entry-name>          <container-type>PortalRuntimeContainer</container-type>       </module>    </modules-additional> </application-j2ee-engine>

 

application.xml:

<?xml version="1.0" encoding="UTF-8" ?>   <application>     <display-name>com.sap.xyz.sample</display-name>   </application>

 

com.sap.xyz.sample-dd.xml:

<?xml version="1.0" ?> <SDA>   <SoftwareType>J2EE</SoftwareType>   <engine-deployment-descriptor version="2.0"/> </SDA>

 

When the ear is deployed, the UWL service should be running, and it uploads the XML configuration file and registers it with the medium priority.