Viewing Artifacts

When you check out a business service, the View Artifacts to Check Out form displays. A list of the artifacts associated with the business service displays in the grid. Everything in this grid will be downloaded from the deployment server to the client server.

Access JD Edwards EnterpriseOne OMW.

1. Open the project in which the business service object resides, and then select the business service object that contain the artifacts you want to view.

2. Click Design.

3. On the Design Tab, click the View Checked in Artifacts button.

   The View Checked in Artifacts form displays. This form provides information about the artifacts that comprise the business service in a specific pathcode. This form provides only limited information on what artifacts are present for the business service on the local development client. The artifact file you want to view is on your local machine. This file is different on the server than it is on your local machine.

4. View the following fields for artifact information:

   • Business Service Name

   • Package Prefix

   • Pathcode: This field contains the pathcode from which the information is being retrieved.

   • Published Class Name: This field indicates if an artifact in the business service is published. The field is populated with the name of the artifact that is published in the business service. This artifact is a Java class that defines which business service operations in the business service are accessible from the Web Services server. If this field is blank then this business service is not published.

5. In the grid located at the bottom of the form, EnterpriseOne displays a list of all of the artifacts that make up the business service in the specified pathcode. Each grid record indicates the artifact name, the artifact internal path, and the artifact state description.

   The artifact internal path is made of many folders that are nested inside the business service root folder. The root folder of a business service is as follows:

   <E1 install folder>\<pathcode folder>\java\source\<package prefix>\<Business Service name>

   For example, if you have business service JPTEST on a DV812 client, and the package prefix is oracle.e1.bssv. JPTEST's root folder is as follows:

   C:\B9\DV812\java\source\oracle\e1\bssv\JPTEST\

   Furthermore, if the grid lists an artifact named testing.java, and the internal path is util\testing, then the full path to testing.java on the development client will be as follows:

   C:\B9\DV812\java\source\oracle\e1\bssv\JPTEST\util\testing\testing.java

   The last two columns in the grid indicate the state of the artifact. The state can be either that the artifact was checked into the pathcode but is not currently found on the local client, or that the artifact was checked into the pathcode and is also currently found on the local client.

6. Click OK.