Understanding the Build Process for a Business Service Package

When building a business services package for WLS & WAS, the JD Edwards EnterpriseOne System:

1. Creates the \\work\sbf\sbfbuild.ini, which defines the paths to the exposed methods.

2. Creates the Ant scripts, logtimestamp.xml and build.xml, in the \\work\sbf directory.

3. Runs the build.xml Ant script to extract source.

   When the extract occurs, Unjar_BusinessService.log is generated in the \\work\sbf directory.

4. Creates Java Web Service (JWS) files.

   The JWS files are created on the EnterpriseOne Deployment Server in the E1_Install_Path\Pathcode\Package\PackageName\java\sbf\sbfjaxwswls directory for WLS and at E1_Install_Path\Pathcode\Package\PackageName\java\sbf\sbfjaxwswas directory for WAS.

   A JWS file is created for each published business service, and it has annotations that describe the published business service. The selected methods are listed in the created published business service. The JWS files are required to create the WSDL artifacts for the published business services, and they should not be edited manually.

5. Creates the Web Service Inspection Language (WSIL) file, which is used for Business Process Execution Language (BPEL).

6. Creates Ant scripts for WLS and WAS.

   These scripts are named build.compile.xml, build.xml, and sbfwebservices.xml. They are created within the \\work\sbf\wls directory for WLS and within the \\work\sbf\was directory for WAS.

7. Runs the build.xml Ant script.

   The build.xml Ant script:

   1. Creates javadoc.

   2. Compiles the business services java source files.

   3. Invokes the sbfwebservices.xml Ant script to run the wsgen Ant task

      Invokes the sbfwebservices.xml Ant script to run the wsgen Ant task to create the web services artifacts (such as the WSDL file).

   4. Generates the required deployment descriptors, and assembles the business services classes into an .ear file that is compatible with WLS and WAS.

When the build process finishes, an E1Services-Pathcode-wls.ear file is created for WLS, and an E1Services-Pathcode-was.ear file is created for WAS on the EnterpriseOne Deployment Server within the E1_Install_Path\Pathcode\Package\PackageName directory.

Note: For WLS, review the wls_BusinessService.log in the \\work\sbf\wls directory and for WAS, review the was_BusinessService.log in the \\work\sbf\wls directory to verify that the build was successful. If the build is successful, Build Successful appears at the bottom of the log. If the build failed, Build Failed appears at the bottom of the log.