1 Understanding the Transaction Server Components

This chapter describes:

1.1 Overview

The JD Edwards EnterpriseOne Transaction Server Components installer performs the installation, upgrade, and configuration of the Transaction Server Components. These components provide the Real Time Events functionality on the Transaction Server.

This document is not a substitute for the administration manuals provided by your IBM WebSphere Application Server vendor, the network administration manuals provided by your network vendor, or the installation and configuration manuals for third-party products used with JD Edwards EnterpriseOne.

The procedures in this guide support the IBM WebSphere Application Server. This document is designed for management information system (MIS) managers and installers. To successfully install the Transaction Server Components on an Application Server, you must have a working knowledge of these topics:

  • Hardware and software requirements

  • IBM WebSphere Application Server setup and administration

  • JD Edwards EnterpriseOne platforms and operating systems

The recommended method of obtaining this information is to attend the relevant training courses. Information about course offerings, dates, and locations is available on My Oracle Support. At a minimum, read these guides before beginning:

1.2 Certifications (Formerly Known as Minimum Technical Requirements)

Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne Certifications (formerly known as Minimum Technical Requirements). In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the following link for cross-reference material in the Program Documentation for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products.

http://www.oracle.com/corporate/contracts/index.html

Refer to the Certifications tab on My Oracle Support and search for this product:

  • JD Edwards EnterpriseOne Transaction Server.

For additional information on using Certifications, refer to this document on My Oracle Support (https://support.oracle.com):

  • Certifications FAQ for JD Edwards EnterpriseOne [Article ID 1525328.1]

1.3 Obtaining the Transaction Server Managed Software Component

You can obtain the Transaction Server Managed Software Component from:

  • Update Center

  • Change Assistant

The name of the component to download is called 91xTy, where x is the major tools release (for example, 9.1) and y is the maintenance release. For example, the Managed Software Component for the Transaction Server for 9.1.3.0 is called 91T30.

Note:

Once obtained, the Transaction Server Managed Software Component is installed using the JD Edwards EnterpriseOne tool called Server Manager. Refer to the JD Edwards EnterpriseOne Server Manager Guide for additional details.

1.4 Prerequisites

These prerequisites are required prior to installing the Transaction Server Components on an Application Server.

  • IBM WebSphere Application Server must be installed, configured and running. Refer to this document for JD Edwards EnterpriseOne-specific installation instructions for the application servers (including patches):

    JD Edwards EnterpriseOne 9.1.X HTML Server Certifications (Doc ID 1506201.1)

  • Verify that your installation meets the prerequisites for installing the IBM WebSphere Application Server at this link:

    http://www-01.ibm.com/software/webservers/appserv/was/library/index.html

1.5 Understanding Transaction Server Communications

The JD Edwards EnterpriseOne Server Manager communicates with the Transaction Server using JMX (Java Management Extensions). The Embedded Agent in the Transaction Server does not connect to HTTP nor does it connect using Plugins. This is the mechanism by which Server Manager manages the Transaction Server.

The Embedded Agent generally allocates ports in an incremental manner. For example, if a Server Manager Agent installed on the machine is running on port number 14502 (default) then the Embedded Agents running inside managed instances on that machine would allocate ports starting from 14502+1=14503, 14504, and so on depending on the number of managed instances on that machine.

Tip:

In order to ascertain the Port Number on which the Transaction Server Embedded Agent is running, open the SystemOut.log file of the WebSphere J2EE Container and search for the string *Management Agent* which should take you to a line containing this string: 
00000017 Server I Starting the management agent listener on port '14503'

The Transaction Server communicates with the JD Edwards EnterpriseOne Enterprise Servers using the EnterpriseOne Proprietary Communication Protocol; that is, JDENET messages.

The Transaction Server connects to the JD Edwards EnterpriseOne database using proprietary database middleware (JDBj). The default ports are dependent on the database type:

  • 1521 for Oracle database

  • 1433 for SQL Server database

  • 50000 for DB2 database

Although the above are default ports, it is possible to run these databases on different ports. Further, these ports are only defined for the Bootstrap database. The JDBj code retrieves the port numbers for the other databases from the Data Source Master Table based on the port numbers for each of the Data Source records as configured during the Planner and Workbench and the Work with Data Sources Application.