Build Process for WAS

For 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 service interface files.

   An interface file is created for each published business service. The selected methods are listed in the created published business service.

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

6. Creates Ant scripts for WAS.

   These scripts are created within the \\work\sbf\WAS directory.

7. Runs the WAS build.xml Ant script.

   The build.xml script creates an .ear file that is WAS-compatible.

8. Compresses the java folder for deployment of the client sbf.cab.

   Note: Review the was_BusinessService.log 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.