This chapter contains the following topic:
The business services server enables JD Edwards EnterpriseOne to natively produce and consume web services. The business services server, which is built on top of a Java 2 Platform, Enterprise Edition (J2EE) server, can be an Oracle Application Server or a WebSphere Application Server. The business services server is required for creating JD Edwards EnterpriseOne provider and consumer web services. Applications that are developed or run on the business services server are written in the Java programming language.
When you install the JD Edwards EnterpriseOne software, the Server Manager deploys an application to the application server. This application contains the business service foundation and business service reference implementations. The business service foundation is a collection of executable files that are required for running business services. The business service reference implementations are sample business services that are provided by JD Edwards EnterpriseOne. You can use the reference implementations as models for creating custom business services that can be exposed as web services. A reference implementation for creating web services for JD Edwards EnterpriseOne as a web service consumer is provided.
Security for the JD Edwards EnterpriseOne business services consists of two main categories—authorization and authentication.
Access to run published business services is managed through the JD Edwards EnterpriseOne Security Workbench. For published business services, JD Edwards EnterpriseOne uses a secure by default security model, which means that users cannot run a published business service unless a security record exists that authorizes access.
Authentication for consuming JD Edwards EnterpriseOne business services uses standard JD Edwards EnterpriseOne user credentials or anonymous login.
Business service security ensures that business service consumers are authenticated in JD Edwards EnterpriseOne and are authorized to use the business services. The business services server uses the JD Edwards EnterpriseOne Login Module to ensure that consumers are authenticated. The module uses Java authentication and authorization service (JAAS) to validate the JD EnterpriseOne users against the EnterpriseOne Security Server. Alternatively, to give non-JD Edwards EnterpriseOne users access to business services, you set up an anonymous user login in the jdbj.ini file.
See Also:
JD Edwards EnterpriseOne Tools Business Services Server Reference Guide on the My Oracle Support Web site.
Scalability for the JD Edwards EnterpriseOne business services server depends on scalability features provided by the host application server—Oracle Application Server or WebSphere Application Server.
When a component or machine in the system goes down or is brought down, other components and machines in the system should gracefully degrade and reconnect when the component or machine is back up. A system is considered to be fault-tolerant when these conditions exist:
Error messages to the user and administrator are meaningful when a component of the system cannot be contacted.
Connections can be reestablished when a component of the system is restarted without administrative interaction on other components of the system.
The components that are relevant for the business services server to be fault-tolerant are the enterprise server and the security server.
The connection to the enterprise server is fault-tolerant. If the enterprise server is down, the exceptions that are returned from a called web service are descriptive and indicate the problem. When the enterprise server comes back up, subsequent web service calls connect correctly without restarting or any further administration of the business services server. If connections to the enterprise server times out, the connections are reestablished.
The connection from the business services server to the security server is based on a token. If the security server is down or cannot be contacted, the exception message that is returned to the web service caller indicates that the server login failed. When the security server comes back up, the token is validated without administrator interaction.