Understanding Packages for Business Services

After business services are created, they need to be built and deployed for consumption. The package build process builds and creates the necessary files for development client, WebLogic Server (WLS), and Websphere Application Server (WAS) consumption. The client installation process deploys business services to all development clients. The package deployment process deploys the business services archive (.ear) files to the preconfigured J2EE containers on WLS and WAS.

JD Edwards EnterpriseOne supports building JAX-WS based business service packages.

JAX-WS-Based Business Service Packages

Java API for XML-based web services (JAX-WS) is an API for building standards-based web services and clients that are message oriented. JAX-WS supports transmission of SOAP messages over HTTP. JAX-WS delegates data binding-related tasks to the Java API for XML Binding (JAXB). JAXB provides support for Java to XML mapping, additional support for less used XML schema constructs, and also provides bidirectional customization of Java and XML data binding.

JD Edwards EnterpriseOne supports building the following combinations of JAX-WS based business services packages:

JAX-WS package for WLS with JDeveloper 11g.
JAX-WS package for WAS with JDeveloper 11g.
JAX-WS package for WLS with JDeveloper 12c.
JAX-WS package for WAS with JDeveloper 12c.

The business services package includes the JAX-WS based WSDL artifacts for the published business services and the newly developed JAX-WS business service consumer proxies.

Note: You can build JAX-WS business services packages for both WLS and WAS at the same time by selecting both the WLS and WAS options in the Business Services Assembly Application.

Note: Beginning with Tools Release 9.2.1.0, IBM WebSphere Application Server 9.0 is supported.