1. Package Management Guide
  2. Generating Business Service Asset Definition XML Files/Artifacts

Generating Business Service Asset Definition XML Files/Artifacts

To harvest JD Edwards EnterpriseOne published business services artifacts into the Oracle Enterprise Repository server, you have to configure the business services package build process to generate one business service asset definition XML file per published business service (selected in the Assemble Business Services application).

An asset definition XML file contains information about the published business service, such as the name of the published business service, the published method names, the web services description language (WSDL) location of the published business service, and so forth.

To generate the business service asset definition XML files during the business services package build process, add the following parameter and value to the MTR VALIDATION section of JD Edwards EnterpriseOne jde.ini file for the Microsoft Windows client:

GenerateAssetXml=1
Note: By default, the GenerateAssetXml flag is not present in the JD Edwards EnterpriseOne Windows client jde.ini file. Therefore, the asset definition XML files are not generated by default during the business services package build process.

The following example shows an asset definition .xml file generated for the RI_CustomerManager published business service:

<?xml version="1.0" encoding="UTF-8"?>
<AssetDef xmlns="http://xml.oracle.com/AIA/CAR/V1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xml.oracle.com/AIA/CAR/V1 auasset.xsd">    
<Instance>
<Core>
<UID>
<AssetType>JDEdwardsE1: Business Service</AssetType>        
<TargetNameSpace>http://xml.oracle.com/JDEdward/EnterpriseOne</TargetNameSpace>        
<Name>JPR01020.RI_CustomerManager</Name>        
<Version>E812</Version></UID>
<Description>RI_CustomerManager</Description>        
<LocationURL>Actual WSDL URL of PBSSV to be set here after BSSV Package Deploy</LocationURL>
<Dynamic>
<Name>getCustomerCreditInfo</Name>
<Value>Published method for getCustomerCreditInfo retrieves credit information for Customer using provided entity id.
       Acts as wrapper method, passing null context and null connection, will call protected getCustomerCreditInfo.
       This is a reference implementation for getting customer credit information, it should not be used in Production.
</Value>
</Dynamic>
<Category>
<ApplicationName>JD Edwards EnterpriseOne</ApplicationName>        
<Keywords/></Category></Core>
<Extend>
<Category>
<Name/>
<Value/></Category>
<Attribute>
<Name>Application Release</Name>
<Value>E812</Value></Attribute>
<Attribute>
<Name>Production Code</Name>
<Value>H95</Value></Attribute>
<Attribute>
<Name>Production Code Description</Name>        
<Value>Object and Environment Tech</Value></Attribute>        
<Attribute>
<Name>Published Business Service Class</Name>        
<Value>oracle.e1.bssv.JPR01020.RI_CustomerManager</Value></Attribute> 
<Attribute>
<Name>Java Doc Location</Name>
<Value>rep://JDEdwardsE1: Business Service:DV812_JAVA_DOC/oracle/e1/bssv/JPR01020/RI_CustomerManager.html</Value></Attribute>        
<Attribute>
<Name>Java Doc URL</Name>
<Value>click here for Java Doc for RI_CustomerManager</Value>
</Attribute>
</Extend>
</Instance>
</AssetDef>

When the business services package build process completes successfully, the generated asset definition XML files are placed on the deployment server at: 

DEP_SERVER\APP_RELEASE\PATHCODE\PACKAGE\PACKAGENAME\ASSETDEFNFILES