JD Edwards EnterpriseOne

Tools Release 8.97

Business Services Server Reference Guide

November 2007

JD Edwards EnterpriseOne Tools Release 8.97 Business

Services Reference Guide

Copyright © 2007, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are
provided under a license agreement containing restrictions on use and disclosure and are also protected by
copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or
decompilation of the Programs, except to the extent required to obtain interoperability with other independently
created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the
documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may
be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced
or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf
of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal
Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure,
modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the
licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional
rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle
Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous
applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other
measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim
liability for any damages caused by such use of the Programs.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle
is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks
associated with the use of such content. If you choose to purchase any products or services from a third party, the
relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party
products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of
products or services and warranty obligations related to purchased products or services. Oracle is not responsible for
any loss or damage of any sort that you may incur from dealing with any third party.

Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.

Open Source Disclosure

Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentation
and disclaims any and all liability or damages resulting from use of said software or documentation. The following
open source software may be used in Oracle's PeopleSoft products and the following disclaimers are provided.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright (c) 19992000
The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED “AS IS’’ AND ANY EXPRESSED
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Table of Contents
 Chapter 1 – Understanding Business Services Server ............................................. 1
Business Services Server Overview ................................................................................1

Server Manager ..............................................................................................................1

Chapter 2 - Configuring Business Services Server 1

Setting Up Business Services Server Logging...............................................1
Setting Up Web Service Logging.............................................................................1
Configuring the Business Services Server for Consuming Web Services......2
Understanding Business Services Server Configuration for Consuming Web Services
..............................................................................................................................2
Configuring JDENet .................................................................................................2
Configuring an HTTP Proxy Server .........................................................................4
Business Services Server Fault Tolerance ....................................................7

Chapter 3 - Configuring Business Services Server Security 12

Understanding Business Services Server Security........................................12
Setting Up Anonymous Login ........................................................................13
Understanding Anonymous Login............................................................................13 Configure
Oracle Application Server to Use Anonymous Login..............................14
Configure WebSphere to Use Anonymous Login....................................................15
Enabling SSL for HTTP Request/Reply.........................................................17
INI Configuration Changes for Communication Over SSL.......................................17
Configuring Production Application Server to Work with Certificates......................18

Chapter 4 - Troubleshooting Business Services Server 30

Exceptions.....................................................................................................30
SOAP Faults.............................................................................................................30
JD Edwards EnterpriseOne System Exceptions......................................................30
JD Edwards EnterpriseOne Application Exceptions/Errors .....................................31
JD Edwards EnterpriseOne Application Warnings.........................................31
Business Services Server logs ......................................................................32

Copyright © 2007, Oracle. All rights reserved 11/8/07 i

Chapter 1 – Understanding Business Services
Server
This chapter discusses:

• Business Services Server overview

• Server Manager

Business Services Server Overview

The Business Services Server enables JD Edwards EnterpriseOne to natively
produce and consume web services. The Business Services Server is built on top of
a Java 2 Platform, Enterprise Edition (J2EE) server, which can be an Oracle
Application Server or a WebSphere Application Server. Applications that are
developed or run on the business services server are written in the Java
programming language.
This guide does not provide instructions on how to install the Business Services
Server; it provides other Business Services Server configuration that you should
consider, such as security options and logging.
For information about installing and setting up a Business Services Server, see:

• “Create a Business Services Server as a New Managed Instance” in the

Server Manager Guide.
This section contains information on how to use Server Manager to install a
J2EE container on the machine that you want to use as your Business
Services Server.

• Working with Packages for Business Services in the JD Edwards

EnterpriseOne Tools 8.97 Package Management Guide.
This section contains information on how to use the JD Edwards
EnterpriseOne Package Deployment and Tools applications to build a
package that contains business services and deploy that package to the
J2EE container installed by Server Manager.

Server Manager
Beginning with JD Edwards EnterpriseOne Tools Release 8.97, a new tool called
Server Manager is provided. This tool is a complete replacement for the JD Edwards
EnterpriseOne legacy management and installation tools including internal
components known as Server Administration Workbench (SAW), Server

Copyright © 2007, Oracle. All rights reserved 11/8/07 1

Chapter 1 – Understanding Business Services Server

Management Console (SMC), and the InstallShield based installers previously used
to install or upgrade JD Edwards EnterpriseOne servers. As a result, you should
refer to the JD Edwards EnterpriseOne Server Manager Guide for details on
installing and configuring all JD Edwards EnterpriseOne server products. This guide
only contains reference information for functionality outside the Server Manager tool.

Note.
Management of JD Edwards EnterpriseOne Tools Release 8.96 or earlier must be
done using the existing tools. Server Manager cannot be used to manage any JD
Edwards EnterpriseOne Tools Release prior to 8.97

The Server Manager tool provides:

• Configuration Management
Server Manager provides a web-based interface for managing the
configuration of each managed server. Each configuration item is accessible
along with integrated help describing the configuration setting.

Note.
Beginning with the availability of Server Manager, it is strongly advised that all
configuration changes to configuration files (such as jde.ini, jas.ini, jdbj.ini,
jdelog.properties, and so on.) for any JD Edwards EnterpriseOne server managed by
Server Manager be accomplished only through the Management Console interface
of Server Manager. In addition to usability improvements, using Server Manager
reduces the risk of introducing configuration errors by providing drop-down lists with
the only valid values where applicable. Further, the tool provides a useful Audit
History for any modifications made to configurations using Server Manager.

• Audit History
Server Manager maintains a history of changes made to the managed
servers. This includes a history of each configuration change, each server
start and stop, and each tools release update, including the user that
performed the change or operation. The information is logged to a history file
that you can query from within Server Manager.

• Configuration Comparison
Use Server Manager to compare the configuration of two or more servers to
identify configuration differences. This can be done directly through the
Management Console application regardless of the platform or location of the
actual JD Edwards EnterpriseOne server. You can also compare individual
servers with the default configuration of the corresponding server group to
which the server belongs.

Copyright © 2007, Oracle. All rights reserved 11/8/07 2

Chapter 1 – Understanding Business Services Server

• Web Based System Management

You can securely access and manage your JD Edwards EnterpriseOne
installation from anywhere using a standard web browser.

• Remote Deployment and Upgrades

You can install, uninstall, and update your JD Edwards EnterpriseOne
servers regardless of their physical location or platform.

• Remote Operational Control

You can start and stop any of your JD Edwards EnterpriseOne servers,
Oracle J2EE application servers, or third party J2EE application servers
directly through the Management Console.

• Secure Administrative Tasks

Server Manager permits you to specify which existing JD Edwards
EnterpriseOne users that may access the Management Console, including
which servers users are allowed to view within the Management Console,
and which administrative tasks users may perform on those servers for which
the user is allowed to view.

• Integrated EnterpriseOne Software Management

Use Server Manager to centrally maintain all your JD Edwards EnterpriseOne
server tools releases, including the ability to copy the software to the remote
server machines.

• Logical Server Grouping

Server Manager allows grouping similar purposed servers into a logical
grouping. These groups can include any of the server types such as
Enterprise Server, Web Server, and so on. A default, or template,
configuration is maintained for each server group.

• Application Release Independence

Server Manager is delivered with JD Edwards EnterpriseOne Tools Release
8.97 and is compatible with any supported JD Edwards EnterpriseOne
application release beginning with Application Release 8.9 through the
currently supported release. There are no electronic software updates
(ESUs) required to support Server Manager.

• Self-Contained Installation
The installation Server Manager delivers all components that are necessary
for the tool to run. There are no third-party requirements regardless of your
existing or intended middleware topology (for example, Oracle Application
Server, WebSphere Application Server, or no application server.

• Tools Release Independence

Copyright © 2007, Oracle. All rights reserved 11/8/07 3

Chapter 1 – Understanding Business Services Server

The current version of Server Manager can be used regardless of the service
pack level of JD Edwards EnterpriseOne Tools Release 8.97 or later of the
managed JD Edwards EnterpriseOne servers.

Copyright © 2007, Oracle. All rights reserved 11/8/07 4

Chapter 2 - Configuring Business Services
Server
This chapter discusses:

• Setting Up Business Services Server logging.

• Configuring the Business Services Server to consume web services.
• Allowing a PS_TOKEN to be received by the E1 Login Module
• Business Services Server fault tolerance.

Setting Up Business Services Server Logging

This section provides an overview of business service logging and discusses how to
set up web service logging.
The business service framework package provides an interface that provides logging
utilities for activities related to published business services and business services.
You use log files to troubleshoot system behavior. The location of the business
service and published business service log files is defined in the jdelog.properties
file.
At runtime, the system updates the log file with these kinds of errors:

• Severe
• Warning
• Application
• Information

Setting Up Web Service Logging

You can set up your system to log SOAP errors.

► To set up web service logging when using Oracle Application Server

1. Enter thisURL for the application server control: http://<server>:<port>/em

For example: http://<server ip>:8888/em.

The application server control appears.

2. Enter your log in credentials.

3. Click login.

Copyright © 2007, Oracle. All rights reserved 11/8/07 1

Chapter 2 - Configuring Business Services Server

4. On the home page, access the Enable/Disable Features page using this
navigation:
Click the Web Services tab, web service link, Administration tab, and then
Enable/Disable Features.

5. In the Enable/Disable Features page, select Logging or Auditing (or both)

from the Available Features list, and then click Move to shuttle them to the
Enabled Features list.
6. Click OK.
7. On the Administration tab, use the Edit Configuration to select the features
that you want to audit.
8. Invoke the web service operations a few times.
9. Use this address in Microsoft Windows Explorer to view the log file:
<JDEV_HOME>\j2ee\home\log\wsmgmt\auditing\log.xml.

This log shows the header information, arguments passed to the web service,
and values returned by the web service.

Configuring the Business Services Server for

Consuming Web Services
This section provides an overview for configuring the business services server to
enable JD Edwards EnterpriseOne to consume web services and discusses how to:

• Configure JDENet.
• Configure an HTTP Proxy server.

Understanding Business Services Server Configuration for

Consuming Web Services
You must start the JDENet kernel on the business services server so that the
business services server can communicate with JD Edwards EnterpriseOne. You
must also configure the business services server with an HTTP proxy server so that
outgoing connections can be made.

Configuring JDENet
The business services server uses JDENet to communicate with a JD Edwards
EnterpriseOne client (Microsoft Windows or HTML) or JD Edwards EnterpriseOne
enterprise server. The client or enterprise server uses Object Configuration Manager
(OCM) to look up the machine name and port of the business services server.
A JDENet kernel, SBFServerJavaKernel, is started on the Business Services Server.
The business service server listens for messages for this kernel. This kernel listens

Copyright © 2007, Oracle. All rights reserved 11/8/07 2

Chapter 2 - Configuring Business Services Server

for a Ping message and for messages that call a business service. The business
services server response to the Ping message indicates that the kernel is up and
running on the business services server.
Configure these settings in the [JDENET] section of the jdeinterop.ini file on the
Business Services Server:
Parameter Description
serviceNameListen= Enter the port on which the business service server listens for
JDENet messages. The setting for the business services server
and OCM must be the same. The port specified must be
different than the serviceNameConnect port setting.
maxKernelRanges= The maxKernelRanges setting defines the maximum allowed
kernels on the business services server. SBFServerJavaKernel
is the only kernel supported on the business services server,
and this kernel is responsible for processing web service call
messages from the client or enterprise server. Currently, the
only allowed value for this property is 1.

Configure these settings in the [JDENET_KERNEL_DEF1] section of the

jdeinterop.ini file on the Business Services Server:

Note
Values for all of the properties except maxNumberOfThread are static and do not
change.

Parameter Value or Description

krnlName= SBFServerJavaKernel
processClassName= oracle.e1.bssvfoundation.impl.jdenet.SBFServerJavaKernel

startMessageRange= 16201

endMessageRange= 16450

maxNumberOfThread= Defines the number of threads that will be started for the
SBFServerJavaKernel, thereby defining the number of
simultaneous web service call requests the kernel can process.
This maxNumberOfThread value must be set appropriately, based
on call volume, server machine size, and so on.

Configuring an HTTP Proxy Server

The Business Services Server also supports web services consumer functionality.
The Business Services Server is deployed and configured using Server Manager.
This section provides information on the additional configuration for consuming third
party web services.
An HTTP proxy server is commonly used for outgoing HTTP connections. When an
HTTP proxy server is present, all Internet connections are made through the HTTP
proxy server. The business services server might need to make an Internet

Copyright © 2007, Oracle. All rights reserved 11/8/07 3

Chapter 2 - Configuring Business Services Server

connection when calling an external web service. These HTTP proxy parameters are
available for the business services server:
Parameter Description
http.proxyHost The host name of the proxy server.
http.proxyPort The port number of the proxy server.

http.nonProxyHosts Optional. The machines and domains that do not need to be routed
through the proxy server. Typically, these are all machines on the
intranet. Multiple entries must be separated by a vertical bar (|).

http.proxyUser Optional. The user name to be used for authentication on the proxy
server.

http.proxyPassword Optional. The password for the user name that is being used for
authentication.
Configuring an HTTP Proxy Server for an Oracle Application Server

Perform these steps to set up an HTTP proxy server for an Oracle Application
Server’s (OAS) OC4J instance.

► To set up an HTTP proxy on OAS

On Oracle Application Server:

1. Open OPMN configuration file OPMN.XML, which is located in this directory:
<OAS Instal>/opmn/conf

2. Locate the configuration for the OC4J instance that is running the business
services server.
You can search for the instance name by searching for the process-type
block in opmn.xml.

3. Under “start-parameters”, add these parameters for “java-options:”

-Dhttp.proxyHost=www-proxy.us.oracle.com -Dhttp.proxyPort=80
Dhttp.proxySet=true
where: proxyHost is the address of proxy
server proxyPort is the port of proxy
server

Your process-type definition should be similar to this example code:

Copyright © 2007, Oracle. All rights reserved 11/8/07 4

Chapter 2 - Configuring Business Services Server

<process-type id="WSCInstance" module-id="OC4J" status="enabled">

<module-data>
<category id="start-parameters">
<data id="java-options" value="-Xrs -server -XX:MaxPermSize=128M
ms512M -mx1024M
-XX:AppendRatio=3 -
Djava.security.policy=$ORACLE_HOME/j2ee/WSCInstance/config/java2.policy
-Djava.awt.headless=true -Dhttp.webdir.enable=false -
Dhttp.proxyHost=www-proxy.us.oracle.com
-Dhttp.proxyPort=80 -Dhttp.proxySet=true -
Doraesb.home=C:\<server ip>\OracleAS_1\integration\esb
-Doc4j.userThreads=true -Doracle.mdb.fastUndeploy=60 -
Dorabpel.home=C:\<server ip>\OracleAS_1\bpel
-Xbootclasspath^/p:C:\<server
ip>\OracleAS_1\bpel/lib/orabpelboot.jar"/> </category>
<category id="stop-parameters">
<data id="java-options" value="-
Djava.security.policy=$ORACLE_HOME/j2ee/WSCInstance/config/java2.policy
-Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
</category>
</module-data>
<start timeout="600" retry="2"/>
<stop timeout="120"/>
<restart timeout="720" retry="2"/>
<port id="default-web-site" range="8889" protocol="http"/>
<port id="rmi" range="12401-12500"/>
<port id="rmis" range="12701-12800"/>
<port id="jms" range="12601-12700"/>
<process-set id="default_group" numprocs="1"/>
</process-type>

Configuring an HTTP Proxy Server for an WebSphere Application Server

Use these steps to set up an HTTP proxy server for an WebSphere Application
Server (WAS).

► To set up an HTTP proxy on WAS

On the IBM WebSphere Application Server:

1. Open the WebSphere Application Server console.
2. In the left navigation pane, click the Application Servers link under Servers.
3. Click the application server that is hosting the business services server.
4. Expand Process Definition on the right, and then click the Java Virtual
Machine (JVM) link.
5. On the JVM properties page, click Custom Properties.
6. Add the required http proxy configuration properties.

Copyright © 2007, Oracle. All rights reserved 11/8/07 5

Chapter 2 - Configuring Business Services Server

• http.nonProxyHosts
• http.proxyHost
• http.proxyPassword
• http.proxyPort
• http.proxyUser
• javax.xml.rpc.ServiceFactory - oracle.j2ee.ws.client.ServiceFactoryImpl
Allow a PS_TOKEN to be received by the JAAS Login ModuleIn order to support all
the mechanisms used by JD Edwards EnterpriseOne for authentication, the
E1LoginModule allows a PS_TOKEN to be received. To use a PS_TOKEN for
authentication, the web service call needs to provide additional information in the
username field. At minimum both "DN=<E1 user id>" and "PS_TOKEN=true" must
be specified. For example:

username - DN=<username>,PS_TOKEN=true

password - PS_TOKEN in string form

In addition, environment and role can be specified in combination with the

PS_TOKEN indicator.

username - DN=<username>,ENV=STGAWSC1,ROLE=*ALL,PS_TOKEN=true

password - PS_TOKEN in string form

The sequence and case of the username values are not significant.

Business Services Server Fault Tolerance

When a machine in the system goes down or is brought down other machines in the
system should gracefully degrade while it is down and reconnect once it is back up.
For the Business Services Server the relevant machines are the Security Server and
the Enterprise Server. The connection to the Enterprise Server is fault tolerant. If the
Enterprise Server is down, the SOAP faults thrown from a called web service are
descriptive and indicate the problem. If 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 time out the connections are reestablished.

Note
When the security, and enterprise servers are bounced, or kernel recycling has
occurred, the Business Services server does not need to be bounced.

The Business Services Server handles:

• Expired Security Tokens

Copyright © 2007, Oracle. All rights reserved 11/8/07 6

Chapter 2 - Configuring Business Services Server

• Disabled E1 User accounts after the Business Services Server has already
acquired the token
• Timeout of the Java Connector Session
• Timeout of the JDBj Connection
• Communication with Enterprise Server is Unavailable

Expired Security Tokens

The connection from the Business Services Server to the Security Server is based
on a token. If the security server is down or can't be contacted the exception thrown
to the web service caller indicates that server login has failed. When the security
server comes back up, the token can be revalidated as necessary without any
administrator interaction.
When the first published Business Services call makes a new connection after the
security token expires:

• The cache is removed for available connections and the token

• Active connections to be removed after completion are flagged
• If the current published Business Services and underneath Business Services
call has already used connections and performed any operation (DB/BSFN),
the published Business Service call fails and Business Services runtime
throws the runtime error to the published Business Services caller
(orchestration layer). Next the published Business Services creates a new
token and connections are created and the published Business Services
succeeds.
• If no connection has been used by the current published Business Services a
new token and connections are created and the published Business Services
succeeds

Disabled E1 User accounts after the Business Services Server has already
acquired the token
When an EnterpriseOne user account becomes disabled:

• The Business Services Server JAAS authentication has the security token
cached by credentials
• The cached token gets revalidated after the configurable setting is passed
(default is 1 hour)

This happens in the next published Business Services call with same
credentials

The JAAS authentication module will detect this and follows the same
pattern as Token Expired

Copyright © 2007, Oracle. All rights reserved 11/8/07 7

Chapter 2 - Configuring Business Services Server

Timeout of the Java Connector Session

The first Business Services Call after the timeout detects that the session has timed
out and removes all cached connection information and recreates a new session
using the existing security token.

Timeout of the JDBj Connection

This only happens when security token times out.

Communication with Enterprise Server is Unavailable

When the Enterprise Server connection is re-established (server bounced) or the
CallObject Kernel on the Enterprise Server expires the first published Business
Service called with any credentails are in principal cache. The cached business
function connection is retrieved from the connection pool and the remote
environment with the jdekrnl no longer exists. When the business function is
executed a system error is received and the following cleanup is performed:

• The cache for available connections and tokens are removed.

• The active connections with these credentials that are to be removed are flagged.
A system exception error for this business function is thrown and you are asked to try
again.
Expired Server Log Errors

This section describes the log errors for:

• JD Edwards EnterpriseOne Security Server is down.

• JD Edwards EnterpriseOne HTML Web Server is down.
• JD Edwards EnterpriseOne Business Services Server is down.

JD Edwards EnterpriseOne Security Server is Down

When the JD Edwards EnterpriseOne Security Server is down, the Business
Services log displays this error message:

17 Sep 2007 16:37:20,281 [Line ?] [main] [SEVERE] - [INTEROP]

Cannot connect to any OneWorld Security Server.FAILURE: null
com.jdedwards.system.connector.dynamic.ServerFailureException: Cannot
connect to any OneWorld Security Server.FAILURE: null
com.jdedwards.system.connector.dynamic.ServerFailureException: Cannot
connect to any OneWorld Security Server.FAILURE: null

at com.jdedwards.system.connector.dynamic.Connector.loginBase(Unknown
Source)
at com.jdedwards.system.connector.dynamic.Connector.login(Unknown Source)
at oracle.e1.bssvfoundation.impl.security.E1Principal.login(Unknown

Copyright © 2007, Oracle. All rights reserved 11/8/07 8

Chapter 2 - Configuring Business Services Server

Source)

at
oracle.e1.bssvfoundation.impl.security.PrincipalCache.getIniPrincipal(Unknow
n Source)
at oracle.e1.bssvfoundation.impl.jdenet.CallSBFHandler.callSBF(Unknown
Source)
at
oracle.e1.bssvfoundation.base.TestBusinessService.callBSSVWithXMLFile(Unknow
n Source)

at
oracle.e1.bssv.JTRH90I10.RI_HTTP_ParseTransformSendMessage.main(RI_HTTP_Pars
eTransformSendMessage.java:22)

17 Sep 2007 16:37:20,281 [Line ?] [main] [DEBUG ] - [BSSVFRAMEWORK]

[Context ID: ] Login failed
Cannot connect to any OneWorld Security Server.FAILURE: null

17 Sep 2007 16:37:20,500 [Line ?] [main] [DEBUG ] - [INTEROP]

Connector shut down completely

JD Edwards EnterpriseOne HTML Web Server is Down

When the HTML Web Server is down, the Business Services log displays this error
message:

Note
In this example, the HTML Web Server is on localhost/6081.

17 Sep 2007 16:27:08,375 [Line ?] [main] [DEBUG ] - [BSSVFRAMEWORK]

[Context ID: <server ip>:2189:1190068027906:0] HTTPAdapterService default
connection created.
17 Sep 2007 16:27:08,375 [Line ?] [main] [DEBUG ] - [BSSVFRAMEWORK]
[Context ID: <server ip>:2189:1190068027906:0] Executing POST opeartion
on the
URL:http://LOCALHOST:8888/LOCALDEV/HTTPCallbackListenerServlet?uname=Vus9V0B
lQWTtx6skDxhDEw%3D%3D&env=STGACLM&role=*ALL&token=SXN9hg6sFNEhk3u1p11TXAbMmO
CIq7MematY%2FxRz0VnY2Fg4HzYzGIa4DUF%2FBoBf1SnRgakeIoxol2jKPaU4vC0GEAB%2BwmGV
xsm1Upgf%2BKx5mrcBaAOIRJI0WeYuB9F90K355TTaHt2DCrGgA9Q0yyQBG64npYURcZBGNla%2F
satjvcgIEYwumORJlsGoRISzpJl5O8vswYM%2BKw5O1iMYfL%2B3E1lDmS5UXzuTwz0j3KibdkV2
UngEj9hKxJjRXUAWb6fxf4TYLHGql7GNUmsMTvLZKPFk1sKdtTzF49FaYwLeRYO7zBs4RVnU1mPh
UNnF&bssv=oracle.e1.bssv.JPRH90I0.RI_HTTPResponseManager&bssvMethod=executeX
APICallMethod&xCID=176914329&xCPort=6080&xMagicNo=1&xBSFN=NotThereYetBSFN
17 Sep 2007 16:27:08,375 [Line ?] [main] [DEBUG ] - [BSSVFRAMEWORK]
[Context ID: <server ip>:2189:1190068027906:0] Connecting to the
URL:http://LOCALHOST:8888/LOCALDEV/HTTPCallbackListenerServlet?uname=Vus9V0B
lQWTtx6skDxhDEw%3D%3D&env=STGACLM&role=*ALL&token=SXN9hg6sFNEhk3u1p11TXAbMmO
CIq7MematY%2FxRz0VnY2Fg4HzYzGIa4DUF%2FBoBf1SnRgakeIoxol2jKPaU4vC0GEAB%2BwmGV

Copyright © 2007, Oracle. All rights reserved 11/8/07 9

Chapter 2 - Configuring Business Services Server

xsm1Upgf%2BKx5mrcBaAOIRJI0WeYuB9F90K355TTaHt2DCrGgA9Q0yyQBG64npYURcZBGNla%2F
satjvcgIEYwumORJlsGoRISzpJl5O8vswYM%2BKw5O1iMYfL%2B3E1lDmS5UXzuTwz0j3KibdkV2
UngEj9hKxJjRXUAWb6fxf4TYLHGql7GNUmsMTvLZKPFk1sKdtTzF49FaYwLeRYO7zBs4RVnU1mPh
UNnF&bssv=oracle.e1.bssv.JPRH90I0.RI_HTTPResponseManager&bssvMethod=executeX
APICallMethod&xCID=176914329&xCPort=6080&xMagicNo=1&xBSFN=NotThereYetBSFN

17 Sep 2007 16:27:09,531 [Line ?] [main] [SEVERE] - [BSSVFRAMEWORK]

[Context ID: <server ip>:2189:1190068027906:0] Connection refused:
connect java.net.ConnectException: Connection refused: connect
java.net.ConnectException: Connection refused: connect

17 Sep 2007 16:27:09,531 [Line ?] [main] [APP ] - [BSSVFRAMEWORK]

[Context ID: <server ip>:2189:1190068027906:0] HTTP_SERVICE_CALL
Corrective Action :HTTP Service Call Failed
17 Sep 2007 16:27:13,140 [Line ?] [main] [SEVERE] - [INTEROP] Fail
to execute BSFNMethod com.jdedwards.system.kernel.CallObjectSystemException:
COSE#1002 Connection failed: LOCALHOST:6081
com.jdedwards.system.connector.dynamic.ServerFailureException: Fail to
execute BSFNMethod com.jdedwards.system.kernel.CallObjectSystemException:
COSE#1002 Connection failed: LOCALHOST:6081
com.jdedwards.system.connector.dynamic.ServerFailureException: Fail to
execute BSFNMethod com.jdedwards.system.kernel.CallObjectSystemException:
COSE#1002 Connection failed: LOCALHOST:6081

JD Edwards EnterpriseOne Business Services Server is Down

When the Business Services Server is down, the Business Services log displays
these messages:

17 Sep 2007 16:48:33,140 [Line ?]

[EMUI_16_48_33_/console/ias/oc4j/app/appHome] [DEBUG ] - [BSSVFRAMEWORK]
Shutdown JdenetServer complete
17 Sep 2007 16:48:33,187 [Line ?]
[EMUI_16_48_33_/console/ias/oc4j/app/appHome] [DEBUG ] - [BSSVFRAMEWORK]
HTTP Callback Listner Servlet destroyed...

Copyright © 2007, Oracle. All rights reserved 11/8/07 10

Chapter 3 - Configuring Business Services Server Security

Chapter 3 - Configuring Business Services

Server Security
This chapter provides an overview of Business Services Server security and
discusses how to:

• Set up anonymous user login.

• Enable SSL for HTTP Request/Reply.

Note
This chapter covers the authentication of users of business services. For information
about authorizing users to access published business service objects, see “Managing
Published Business Services Security” in the JD Edwards EnterpriseOne Security
Administration Guide.

Understanding Business Services Server Security

JD Edwards EnterpriseOne provides authentication security to ensure that published
business service users are authenticated in JD Edwards EnterpriseOne. The
Business Services Server uses the JD Edwards EnterpriseOne Login Module as the
authentication mechanism for authenticating users against the security server. The
module is automatically installed during the deployment of a JD Edwards
EnterpriseOne business services package to the Business Services Server and
configured for all published services. The module uses Java authentication and
authorization service (JAAS) to validate the JD Edwards EnterpriseOne users against
the JD Edwards EnterpriseOne security server.
To allow access to JD Edwards EnterpriseOne published business services without
providing user credentials, you must set up anonymous login. Anonymous login
directs the application server to use the anonymous login credentials stored in the
jdbj.ini file for user authentication, instead of the E1 Login Module.
See Also:
“Create a Business Services Server as a New Managed Instance” in the Server Manager Guide for
information on how to install a Business Services Server instance.
“Working with Packages for Business Service” for information on how to use JD Edwards
EnterpriseOne to deploy published business services to the Business Services Server.

Setting Up Anonymous Login

This section provides an overview of anonymous login and discusses how to:

Copyright © 2007, Oracle. All rights reserved 11/8/07 11

Chapter 3 - Configuring Business Services Server Security

• Configure Oracle Application Server to use anonymous login.

• Configure WebSphere to use anonymous login.

Understanding Anonymous Login

Anonymous login provides a mechanism to access published business services
without providing JD Edwards EnterpriseOne user credentials. To enable anonymous
login, you must disable the authentication mechanism (E1 Login Module) for a
published business service in the application server. When the authentication
mechanism is disabled, instead of using the user credentials of the consumer of the
published business service for authentication, the application server uses the
anonymous login credentials stored in the jdbj.ini file on the application server. These
credentials are authenticated by the JD Edwards EnterpriseOne Security Server. The
anonymous login password in the jdbj.ini file is encrypted.
You must configure anonymous login for each individual published business service
by disabling the default authentication mechanism for that service. If the
authentication mechanism is not disabled for a published business service, the user
request will be rejected even if the anonymous login credentials have been entered in
the jdbj.ini file.
You use Server Manager to enter these anonymous login credentials in the jdbj.ini
configuration file:

• Bootstrap User
• Bootstrap User Password
• Bootstrap Role
• Bootstrap Environment

Note.
The anonymous login has to be configured every time the Business Services server
is deployed to the server.

See “JDBJ Bootstrap Session” in the Server Manager Guide for information on how to
configure these settings.

Configure Oracle Application Server to Use Anonymous

Login
In Oracle Application Server, you can enable anonymous login for a published
business service or for individual operations within a published business service.

► To set up anonymous login in Oracle Application Server

Copyright © 2007, Oracle. All rights reserved 11/8/07 12

Chapter 3 - Configuring Business Services Server Security

Access Oracle Enterprise Manager.

1. Select the business service OC4J instance.
2. Click the Web Services tab.
3. Select the business service for which you want to enable anonymous login.
4. Click the Administration tab and then click the Edit Security icon.
5. Click Inbound Policies and then clear the “Use Username/Password
Authentication” check box.

Copyright © 2007, Oracle. All rights reserved 11/8/07 13

Chapter 3 - Configuring Business Services Server Security

Configure WebSphere to Use Anonymous Login

In WebSphere, you can disable security for a published business service, which
directs the system to use anonymous login credentials instead.
This section provides an example of turning off the security for the
CustomerManager reference implementation, which is a fully functional example of a
published business service. Use it as an example to help you disable security for a
particular published business service so that the system will use anonymous login
instead.

► To set up anonymous login on IBM WebSphere

1. Locate ibm-webservices-bnd.xmi and ibm-webservices-ext.xmi, which are in

the following two locations:
• WebSphere Home\AppServer\profiles\profile name\config\cells\Cell
Name\applications\Application Name\deployments\Server\Web Module\WEBINF
• WebSphere Home\AppServer\profiles\profile name\installedApps\Cell
Name\Application Name\Web Module Name\WEB-INF
2. Make a backup of these two files in both locations.
3. Using the following example of the RI_CustomerManager web service, delete
the bold text from both the ibm-webservices-bnd.xmi and ibm-
webservicesext.xmi files. You must delete the code from these files in both
locations where the files reside:
• In the ibm-webservices-bnd.xmi, delete the text in bold:
<wsdescBindings xmi:id="WSDescBinding_1185554582312"
wsDescNameLink="RI_CustomerManager">

<pcBindings xmi:id="PCBinding_1185554582312"
pcNameLink="RI_CustomerManagerHttpPort" scope="Application">

<securityRequestConsumerBindingConfig
xmi:id="SecurityRequestConsumerBindingConfig_1185554610375910436757521891737
910436757521891737">

<tokenConsumer xmi:id="TokenConsumer_1185554610375910436757521891737"
classname="com.ibm.wsspi.wssecurity.token.UsernameTokenConsumer"
name="UserTokenConsumer">

<valueType xmi:id="ValueType_1185554610375910436757521891737"
localName="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
usernametoken-profile-1.0#UsernameToken" name="Username Token"/>

<jAASConfig xmi:id="JAASConfig_1186013028227"
configName="e1BssvLogin"/>

<partReference
xmi:id="PartReference_1185554610375910436757521891737" part="UserToken"/>

Copyright © 2007, Oracle. All rights reserved 11/8/07 14

Chapter 3 - Configuring Business Services Server Security

</tokenConsumer>

</securityRequestConsumerBindingConfig>

</pcBindings>

</wsdescBindings>

• In the ibm-webservices-ext.xmi, delete the text in bold.

<wsDescExt wsDescNameLink="RI_CustomerManager"
xmi:id="WsDescExt_1185554582328">

<pcBinding pcNameLink="RI_CustomerManagerHttpPort"
xmi:id="PcBinding_1185554582328">

<serverServiceConfig
xmi:id="ServerServiceConfig_118555460310966390350416797703696639035041679770
369">

<securityRequestConsumerServiceConfig
xmi:id="SecurityRequestConsumerBindingConfig_1185554603109663903504167977036
96639035041679770369">

<caller name="basicAuth" part="" uri=""

localName="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
usernametoken-profile-1.0#UsernameToken"/><requiredSecurityToken
xmi:id="RequiredSecurityToken_11855546031096639035041679770369"
name="UserToken" uri=""
localName="http://docs.oasisopen.org/wss/2004/01/oasis-200401-wss-username-
token-profile-
1.0#UsernameToken" usage="Required"/>

</securityRequestConsumerServiceConfig>

</serverServiceConfig>

</pcBinding>
</wsDescExt>
4. Restart the application server

Enabling SSL for HTTP Request/Reply

In JD Edwards EnterpriseOne, you can configure a business service to communicate
with a third-party system using HTTP POST. You can secure communication
between the Business Services Server and third-party sites by using the Secure
Sockets Layer (SSL) protocol.
This section describes:

• INI configuration changes for communication over SSL.

Copyright © 2007, Oracle. All rights reserved 11/8/07 15

Chapter 3 - Configuring Business Services Server Security

• Configuring the production application server to work with certificates.

INI Configuration Changes for Communication Over SSL

The KEYSTORE and TRUST_STORE sections of the jdeinterop.ini file contain
parameters that you must complete to enable SSL for HTTP Request/Reply. When
you create a certificate for communication over SSL, the values that you enter for the
certificate should match the values set for these parameters.
The following parameters in the KEYSTORE section of the jdeinterop.ini are used for
the SSL configuration for HTTP Request/Reply:
Parameter Description
keystorefile= The path to the keystore file.
keystorepasswd= The keystore password.

keyalias= The keystore alias name.

certificatepasswd= The keystore certificate password.

Note
The default settings for these parameters are blank.

The following parameters in the TRUST_STORE section of the jdeinterop.ini are used
for the SSL configuration for HTTP Request/Reply:
Parameter Description
truststorefile= The path to the truststore file. truststorepasswd= The truststore

password.

Note
The default settings for these parameters are blank.

Configuring Production Application Server to Work with

Certificates
This section describes how to:

• Configure the HTTP Adapter Service.

• Configure the Listener Service.

Configuring the HTTP Adapter Service

Perform these tasks to configure the HTTP Adapter Service:

Copyright © 2007, Oracle. All rights reserved 11/8/07 16

Chapter 3 - Configuring Business Services Server Security

• Configure client authentication.

• Check the trustability of the server during handshake.

► To configure client authentication

Create a certificate request (CSR) using keytool.

1. Go to the HTTP Adapter deployed location.
../WEB-INF/classes/.

2. From a command prompt navigate to:

<Business Services deployed location>/WEB-INF/classes/.

3. Use the following commands to create a certificate request:

<JAVA_HOME>\bin\keytool -genkey -keyalg RSA -alias httpclientcer
keystore HTTPAdapterKS.keystore -keypass httpadapter -storepass
httpadapter -dname "CN=Oracle,OU=Oracle,O=Oracle USA L=Redwood
Shores,S=CA,C=US"

Provide all the details for generating the key.

<JAVA_HOME>\bin\keytool -certreq -alias httpclientcer -file clientkeyCSR

keystore HTTAdapterKS.kestore -keypass httpadapter -storepass
httpadapter

The above command generates the certificate request and writes to a file
clientkeyCSR.

4. You obtain the user certificate from a certification authority by submitting the
generated CSR and saving it to a file HTTPAdapter.cer.
5. Obtain the certification authority root certificate (rootCA.cer) and intermediate
CA certificate (rootInterCA.cer).
6. Import the signer certificates rootCA.cer and rootInterCA.cer in to HTTP
Adapter’s keystore using this command:
<JAVA_HOME>\bin\keytool -import -alias rootCAcer -file rootCA.cer
keystore HTTAdapterKS.keystore -keypass httpadapter -storepass
httpadapter

<JAVA_HOME>\bin\keytool -import -alias rootInterCAcer -file rootInterCA.cer

-keystore HTTAdapterKS.keystore -keypass httpadapter -storepass
httpadapter

7. Import the certificate HTTPAdapter.cer in to the HTTP Adapter’s key store

using the following command:
<JAVA_HOME>\bin\keytool -import -v -alias AliasName -file
HTTPAdapter.cer -keystore HTTAdapterKS.keystore -keypass KeyPassword

Copyright © 2007, Oracle. All rights reserved 11/8/07 17

Chapter 3 - Configuring Business Services Server Security

-storepass httpadapter

Where AliasName is the alias of the certificate. This value has to be

updated in the jdeinterop.ini file for keyalias parameter after the certificate
is imported.

Where KeyPassword is the password for the certificate stored in the

keystore. This value has to be updated in the jdeinterop.ini file for property
certficatepasswd after the certificate is imported

► To check the trustability of the server during handshake

Obtain the SSL certificate (ServerRoot.cer) of server’s certificate root CA.

1. Go to the HTTP Adapter deployed location.
../WEB-INF/classes/.

2. From a command prompt navigate to:

<Business Services deployed location>/WEB-INF/classes/.

3. Import the certificate ServerRoot.cer in to the HTTP Adapter’s trust store using
the following command:
<JAVA_HOME>\bin\keytool -import -v -trustcacerts -alias AliasName -file
ServerRoot.cer -keystore cacerts -keypass KeyPassword -storepass
changeit

AliasName – name for alias of the certificate.

KeyPassword – password for the certificate stored in the keystore.

For more details on importing certificate to keystore, please see the documentation of
keytool in Sun’s java documentation.
Configuring the Listener Service

Perform these tasks to configure the listener service:

• Configure SSL for the Listener Service on a IBM HTTP Server.

• Configure SSL for the Listener Service on a OAS Server.

Copyright © 2007, Oracle. All rights reserved 11/8/07 18

Chapter 3 - Configuring Business Services Server Security

► To configure SSL for the listener service on an IBM HTTP Server

1. Open IKeyman tool (ikeyman.bat

under:<IBM_HTTP_SERVER_INSTALL_ROOT>\bin).

2. Create a new Key Database File with Key database type as CMS.

Copyright © 2007, Oracle. All rights reserved 11/8/07 19

Chapter 3 - Configuring Business Services Server Security

3. Provide the password and select stash password to file option.

4. Select Personal certificate requests from Key database content menu and
click New.

Copyright © 2007, Oracle. All rights reserved 11/8/07 20

Chapter 3 - Configuring Business Services Server Security

5. Provide the required information. The Certificate Request File is created at

<IBM_HTTP_SERVER_INSTALL_ROOT>\bin. By default it is certreq.arm.
6. Create a CSR at any Certificate Authority with the Certificate Request
information contained in the Certificate Request File.
Also, obtain Root CA and Intermediate CA certificate from the Certificate
Authority vendor.

7. Select the Signer Certificates option from Key database content.

Copyright © 2007, Oracle. All rights reserved 11/8/07 21

Chapter 3 - Configuring Business Services Server Security

8. Add the Root CA and then Intermediate CA by clicking Add.

Copyright © 2007, Oracle. All rights reserved 11/8/07 22

Chapter 3 - Configuring Business Services Server Security

9. Select the Personal Certificates option from Key database content. Add the
certificate provided by CA by clicking the Receive option
10. Save the file. A key database file with extension .kdb is created.
11. Go to the file <IBM_HTTP_SERVER_INSTALL_ROOT>\conf\httpd.conf Add
the following for VirtualHost:

LoadModule ibm_ssl_module modules/mod_ibm_ssl.so

Listen 443

<VirtualHost <SERVERNAME>.mlab.jdedwards.com:443>

SSLEnable
SSLClientAuth none

</VirtualHost>

SSLDisable

Keyfile "C:\Program Files\IBM\IBM HTTP Server\bin\key.kdb"

Customize it according to your environment.

<SERVERNAME>.mlab.jdedwards.com - DNS Name

Copyright © 2007, Oracle. All rights reserved 11/8/07 23

Chapter 3 - Configuring Business Services Server Security

Keyfile "C:\Program Files\IBM\IBM HTTP Server\bin\key.kdb" –Key Database file

location

12. Go to plugin-cfg.xml Under

<WAS_INSTALL_ROOT>/Plugin/config/webserver1

Note
Webserver1 is the webserver name

Add <Uri Name=”/ListenerService/ ListenerService”/> under the node

UriGroup.

Add <VirtualHost Name=”*:443”/> under node VirtualHostGroup

13. Go to plugin-cfg.xml Under:

<WAS_INSTALL_ROOT>/profiles/default/cells/<SERVERNAME>Node01Cell/
no de/webserver1_node/servers/webserver1

14. Add:
<Uri AffinityCookie=”JSESSIONID” AffinityURLIdentifier=”jsessionid”
Name=”/ListenerService/ListenerService”/> under the node UriGroup.

15. Add:
<VirtualHost Name=”*:443”/> under node VirtualHostGroup

16. Restart WAS.

17. Restart IBM HTTP Server.
18. Deploy the Listener service

See Also

• JD Edwards EnterpriseOne Tools 8.97 Business Services Development

Guide, Appendix B

► To configure SSL for the Listener Service on OAS:

Copyright © 2007, Oracle. All rights reserved 11/8/07 24

Chapter 3 - Configuring Business Services Server Security

1. Go to Oracle wallet manager and create a wallet.

Copyright © 2007, Oracle. All rights reserved 11/8/07 25

Chapter 3 - Configuring Business Services Server Security

2. On New Wallet, complete the Wallet Password and Confirm Password fields
and then click OK.

3. On Oracle Wallet Manager, select the Certificate from the tree, right-click, and
then select Add Certificate Request.

Copyright © 2007, Oracle. All rights reserved 11/8/07 26

Chapter 3 - Configuring Business Services Server Security

4. On Create Certificate Request , enter the appropriate information in the fields

and then click OK.
5. Obtain the following certificates from any Trusted authority using the above
CSR.
• Trusted authority root CA
• Intermediate server CA
• User certificate, which is generated using the CSR.
6. To import the CA certificates into the wallet, on Oracle Wallet Manager, select
the Operations menu, and then select Import Trusted Certificate.
7. To import the user certificate in to the wallet, select the Operations menu, and
then select Import User Certificate.
8. Save the wallet.
9. Update the SSL configuration file
<Oracle_Home>/Apache/Apache/conf/ssl.conf

SSLWallet walletDirectorylocation (Syntax: SSLWallet

file:\\c:\Oracle\Wallets)
SSLWalletPassword passwordofWallet (Syntax: SSLWalletPassword welcome1)

Copyright © 2007, Oracle. All rights reserved 11/8/07 27

Chapter 3 - Configuring Business Services Server Security

10. Restart the Application Server.

11. Deploy the Listener service

See Also
• JD Edwards EnterpriseOne Tools 8.97 Business Services Development
Guide, Appendix B

Copyright © 2007, Oracle. All rights reserved 11/8/07 28

Chapter 4 - Troubleshooting Business Services
Server
This chapter discusses:

• Exceptions
• JD Edwards EnterpriseOne Application Warnings
• Business Services Server logs

Exceptions
When an error occurs an exception will be thrown to the caller. These exceptions fall into
different categories.
This section discusses:

• SOAP (Simple Object Access Protocol) faults

• JD Edwards EnterpriseOne System exceptions
• JD Edwards EnterpriseOne Application exceptions/errors

SOAP Faults
This is most generic of the categories, all exceptions in this category are expressed as
SOAP faults. For example, if something is incorrectly configured on the applications
server or connectivity problems exist you will see these as SOAP faults.

JD Edwards EnterpriseOne System Exceptions

This category includes the things that are wrong inside the JD Edwards
EnterpriseOne space. Most commonly these are server connectivity issues. For
example, if a server is dropped there is an exception thrown to the caller to report
that has happened. The caller will also see an exception if the
authorization/authentication had failed. It is either going to be a temporary system situation
or it is a configuration issue.
This section discusses:

• Server Connectivity
• Authorization / Authentication

Server Connectivity
It is important to be aware that inside the Business Services Server the feature used to
contact the Enterprise server is the Dynamic Java Connector. If the configuration

Copyright © 2007, Oracle. All rights reserved 11/8/07 29

Chapter 4 - Troubleshooting Business Services Server

settings for the Dynamic Java Connector are incorrect it could cause connectivity
problems with the Enterprise server.

Authorization/Authentication

The system is secure by default, if you are getting authorization / authentication errors
it is most likely that you are missing Security Workbench records.

JD Edwards EnterpriseOne Application Exceptions/Errors

Every error that happens within the application logic gets reported as an exception to
the caller. For example; an error in the business data setup, incorrect data passed to
the business data, or a necessary service property could be missing.

JD Edwards EnterpriseOne Application Warnings

Warnings from the JD Edwards EnterpriseOne application are not expressed as exceptions.
Warnings are reported back to the caller in the response information.

Copyright © 2007, Oracle. All rights reserved 11/8/07 30

Chapter 4 - Troubleshooting Business Services Server

Business Services Server logs

Business Services Server logs are configured and accessed through Server Manager.
See JD Edwards EnterpriseOne 8.97 Server Manager Guide: View Log Files

If component level logging is desired there is a new log component called

BSSVFRAMEWORK. When this is enabled, the log file displays system errors and
enables you to gain insight to some application errors.

► To enable component level logging:

1. Access Server Manager.

2. Select a Business Services Server instance.
3. Select Log File Configuration.
4. Enter BSSVFRAMEWORK in the Log Components column for the Business Services
server log.
5. Click the Save button.

Copyright © 2007, Oracle. All rights reserved 11/8/07 31

Chapter 4 - Troubleshooting Business Services Server

Copyright © 2007, Oracle. All rights reserved 11/8/07 32