2 Installation Components

This chapter contains these topics:

2.1 Components of JD Edwards World Service Enablement

The following components are installed when you install JD Edwards World Service Enablement:

  • JD Edwards World A9.2 / A9.2.1 Service Enablement Java application .ear file for either the Oracle WebLogic Application Server (WLS) or the IBM WebSphere Application Server (WAS).

    • For WLS, the file is WebServices_v4_WLS.ear

    • For WAS, the file is WebServices_v4_WAS.ear

    This file contains the Java API .jar file, the Web services files, and all the supporting files. If needed, the file deploys to the application servers and then you can run the Web services.

  • Source code for the services is in the WebServices_v4_SourceFiles.zip. Source code is stored in the .zip files for use in any Java IDE.

  • Javadoc is included to help further explain the Web Services and the underlying source code. The Javadoc is included in the WebServices_v4_Javadoc.zip file.

  • Converged Application Repository files are located in the WorldCARV1.zip. These files are to be used with Oracle Enterprise Repository.

2.2 Application Areas with Installed Web Services

The following lists the JD Edwards World application areas that have Web services installed with World Service Enablement:

  • Address Book

  • Customer Master

  • Supplier Master

  • Item Master Information

  • G/L Account

  • Journal Entry

  • Fixed Asset Master Information

  • Fixed Asset Cost Summary

  • Purchase Order

  • Sales Order

  • Item Master Information

2.3 Oracle Enterprise Repository (OER)

OER serves as the core element to the Oracle SOA Governance solution. An industry-leading metadata repository, OER provides a solid foundation for delivering governance throughout the service-oriented architecture (SOA) lifecycle by acting as the single source of truth for information surrounding SOA assets and their dependencies. OER provides a common communication channel for the automated exchange of metadata and service information between service consumers, providers, policy decision points, and additional governance tooling. It provides the visibility, feedback, controls, and analytics to keep your SOA on track to deliver business value. The intense focus on automation helps to overcome barriers to SOA adoption and streamline governance throughout the lifecycle.

To make it easier to get started with OER, Oracle's Application Integration Architecture (AIA) team has developed an easier way to load services metadata into OER. Called the Converged Application Repository (CAR) project, this is an XML-based front-end to OER.

If you want to have an OER instance on site, you can purchase OER. This allows for loading JD Edwards World Web services metadata using the WorldCARV1.zip after installing JD Edwards World Service Enablement.

Note:

(Release A9.3 Update) To access the Web services for World applications, you must encrypt the SOAP Header password. For more information, see Section 4.2, "Encrypting SOA Password".