Working with Packages for Business Services

This chapter provides an overview of packages for business services and discusses how to:

• Assemble JD Edwards EnterpriseOne business services.

• Assemble a package that contains published business services.

• Build a package with published business services.

• Deploy the package to the Business Services Server.

Understanding Packages for Business Services

This section discusses an overview of packages for business services.

Once business services have been created, they need to be built for Oracle Application Server (OAS) and WebSphere Application Server (WAS) consumption. The package build process creates the necessary .ear files that are consumable by OAS and WAS. Next, the business services need to be deployed. The client installation process deploys business services to all Microsoft Windows 32 clients. The package deployment process deploys the OAS and WAS .ear files to preconfigured J2EE servers.

See Also

Business Services Server Reference Guidefor more information on configuration and security of the Business Services Server

Assembling JD Edwards EnterpriseOne Business Services

This section lists prerequisites and discusses how to assemble business services for package build.

Prerequisites

Before you complete the tasks in this section:

• Use Server Manager to create J2EE business service containers for the Business Services Server.

• Use Server Manager to set up Server Manager users.

  In order to deploy the package successfully, the EnterpriseOne user must be a valid Server Manager user. The user cannot deploy the package if the EnterpriseOne user's credentials are not valid for Server Manager.

  See the JD Edwards EnterpriseOne Tools Release 8.98 Server Manager Guide.

• If the JD Edwards EnterpriseOne client that you are using to build a business services package has been installed with WebSphere Express, you must uninstall WebSphere Express and install IBM Rational Application Developer for WebSphere (RAD). The application for building a package with business services for WAS uses RAD.

• If you have multiple security servers, you must set up EnterpriseOne Trusted Nodes for a successful deployment of business services.

  See Setting Up a Trusted Node Configuration.

Assembling Business Services for Package Build

Enter P9603 in the Fast Path.

1. On the Assemble Business Services form, in the Pathcode field, enter the path code of the package that you plan to build and tab to the next field.

   Note. At this point, the application retrieves all the available business services from F98602 and F98603. If you have used this application before, the application also retrieves the values for the JDeveloper Install Path and Rational Application Developer Install Path fields from the JDE.INI file.

2. If this is your first time in the application, you must manually complete these fields:

   Field	Description
   JDeveloper Install Path	Enter the location where JDeveloper is installed.
   Rational Application Developer Install Path	Enter the location where IBM Rational Application Developer for WebSphere (RAD) is installed. Enter this location only if you will be building a package for WAS.

3. When you enter the install path, P9603 verifies the actual location and version.

   If this path is correct, the P9603 adds the information to the jde.ini:

   [MTR VALIDATION]
   JDeveloperInstallPath=<Install path specified by P9603>
   JDeveloperVersion=10.1.3
   WebSphereInstallPath=<Install path specified by P9603>
   WebSphereVersion=6.1

   Note. If the path or version is incorrect, an error appears; the Close button is disabled until you enter the correct path.

4. In the grid, select the business services that you want to expose as a web service and click the Select button.

   You can also double-click the row headings of the business services that you want to expose.

   A check mark appears by each business service that is selected.

5. Click Select again or double-click the row header to unexpose the web service.

6. Click Close to close the application.

Assembling a Package that Contains Published Business Services

This section discusses how to assemble a business service package.

Assembling a Business Service Package

To set the processing options for Package Assembly, go to the Package and Deployment Tools menu, right-click the Package Assembly application (P9601), and select prompt for values.

1. Set the processing option entitled Business Services to 1. This processing option is blank by default.

2. Select OK.

3. On the Work with Packages form, begin the assembly process.

   See Assembling Packages.

Building a Package with Published Business Services

This section provides an overview of the build process, prerequisites, and discusses how to:

• Define a package build with published business services.

• Resubmit the package build.

Understanding the Build Process

This section provides an overview of how the JD Edwards EnterpriseOne system builds a package that contains business services. 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, the business service.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 OAS.

   These scripts are named build.properties and build.xml. They are created within the \\work\sbf\OAS directory.

7. Creates Ant scripts for WAS.

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

8. Runs the OAS build.xml Ant script.

   The build.xml Ant script:

   1. Creates javadoc.

   2. Compiles java source files.

   3. Assembles all the source into an .ear file that is OAS compatible.

9. Runs the WAS build.xml Ant script.

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

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

    Note. Review the buildservices.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, the business services is flagged as failed; the package still appears to have been built successfully, even though the .ear file is not generated.

Prerequisites

Before building the package, verify that logging is turned off. When the jdeproperties.log file is set for logging in the \system\classes folder and a package build is submitted, the build process is slowed down. It is not recommended to have logging turned on during package builds.

Defining a Package Build with Published Business Services

To define a package build with published business services:

1. Enter P9621 in the Fast Path or go to the Package and Deployment Tools menu and select Package Build.

2. Use the Package Build application to define build properties for the package.

3. On the Package Build Location form, select Client as the Build Location.

   Note. Business services are not built for server-only packages.

The JVM's virtual memory is set to a maximum of 512 MB. You can change this using the following jde.ini settings:

[PACKAGE BUILD]

JavacMaxMemorySize= 512 MB

JavadocMaxMemorySize= 512 MB

Resubmitting the Package Build

If errors occur during the package build, you will need to reset the status and resubmit the package build.

Enter P9622 in the Fast Path or go to the Package and Deployment Tools menu and select Package Build History.

1. On the Work with Package Build History form, enter your package in thePackage Name field and select Find.

2. In the tree structure, expand your package name and CLIENT.

3. Click Business Services and select your business service.

4. Select Reset Status from the Row menu to reset the status of your business services.

5. Select Resubmit Build from the Row menu.

Deploying the Package to the Business Services Server

This section provides an overview of the deployment process and discusses how to deploy the business services.

Understanding the Deployment Process

This is an overview of how business services are deployed to the Business Services Server.

1. When you click Deploy, the R98825F runs.

   Note. If you are deploying the package to both the enterprise server and the Business Services Server, you select the enterprise server and click Deploy. The R98825D then calls R98825F when it is finished.

2. The R98825F creates the scfjar folder.

3. The scf_manifest.xml is created in the scfjar folder.

   This xml contains information that the package deployment process uses to communicate with the server manager.

4. The OAS and WAS .ear files are copied to the scfjar folder.

5. The contents of the scfjar folder are combined to form the bssv_timestamp.jar file.

   Note. If errors occur, they are logged to the jas.log or jasdebug.log files.

6. The jar file is uploaded to Server Manager and both the file and the scfjar folder are deleted from the deployment server.

Deploying the Business Services

Enter P9631 in the Fast Path or go to the Package and Deployment Tools menu and select Package Deployment.

1. On the Work with Package Deployment form, click the Add button.

2. On the Package Selection form, select the business services package to deploy and click Next.

3. On the Package Deployment Targets form, select Business Services Server as the Deployment Target.

   Note. The check box for Business Services Server is disabled if the selected package does not contain business services.

4. On the Package Deployment Attributes form, enter the Management Server URL and click Next.

   Server Manager returns a list of eligible Business Services Servers to which the user can deploy the business services.

   Note. In order to deploy the package successfully, the EnterpriseOne user must be a valid Server Manager user. The user cannot deploy the package if the EnterpriseOne user's credentials are not valid for Server Manager. The user also cannot deploy the package if there is no valid Business Services Server defined in Server Manager.

   See the JD Edwards EnterpriseOne Tools Release 8.98 Server Manager Guide for information about setting up Server Manager users.

5. Select the appropriate servers and click Next.

6. On the Business Services Package Deployment Properties Revisions form, click End.

7. On Work with Package Deployment, open your package name and then Business Service Application Server in the tree structure.

8. Select the date/time stamp and select Deploy from the Row menu.

   Note. You cannot deploy to an individual Business Services Server. Business services are deployed to all servers under the selected date/time stamp.