N JD Edwards Support

This appendix provides a detailed discussion of the support available for the accurate monitoring of JD Edwards EnterpriseOne applications. Note that this support is only available if you have a valid Application Management Suite for JD Edwards EnterpriseOne licence. For more information, contact your Oracle representative.

N.1 Introduction

The monitoring support provided by this version has been verified against JD Edwards installations based on JD Edwards Tools version 8.97 and 8.98 and JD Edwards applications version 8.12. However, JD Edwards applications version 8.11 and 9.0 running on said Tools versions should also work.

N.2 Verifying the Scope of Monitoring

Often the JD Edwards software is configured to use a non-standard port, such as 800. The port on which your JD Edwards installation is running can be found by examining the login URL. This takes the following format:

http(s)://hostname:portnumber/jde/...

Verify the portnumber is configured as one of the defined ports (HTTP or HTTPS). In addition, if a HTTPS port is specified, ensure a copy of the Web server's private SSL key is imported into the Collector system(s).

N.3 Creating JD Edwards Suite Definitions

You can create suite definitions for JD Edwards-based applications in the same way as for any other supported Oracle Enterprise architecture. The procedure to create suites is described in Section 6.5, "Working With Suites".

N.4 Running the create_JDE_info.sh Script

In order for RUEI to correctly translate the JD Edwards business logic within your environment, do the following:

Copy the create_JDE_info.sh script to the home directory of the JD Edwards server. It is located in the /var/opt/ruei/processor/local/download/JDE directory of the RUEI system.
Run the create_JDE_info.sh script as any user on the JD Edwards server.^Foot 1 This script assigns an identification to the identified page IDs within the environment. The create_JDE_info.sh script must be run with the following required parameter:
```
create_JDE_info.sh connect-string
```
where connect-string is the string used to authorize the script to access the JD Edwards database. The script reads from the schemas, and generates .txt files in the current directory. For example:
```
create_JDE_info.sh "sys/oracle@dliild-jde:1522 as sysdba"
create_JDE_info.sh "sys/oracle@JDE as sysdba"
```
Note the connect string must authenticate as "sys as sysdba" to your database. This is because the script tries to detect the correct schema for the various tables used.
The script creates a number of .txt files in the directory where the script is executed. All relevant .txt files are collected and stored in a .zip file. Copy this .zip file to a location that can be used for uploading the files to the RUEI Reporter system.
Select Configuration, then Applications, then Suites, and select the suite you defined earlier.
Specify the name of the .zip file containing the generated .txt files. If you manually create .txt files, you should use the same structure present in the .zip file. To protect against empty definitions, the upload will fail when it contains empty .txt files. When ready, click Upload.

N.5 Verifying the Cookie Technology

When creating a JD Edwards suite instance, a preconfigured cookie for the JD Edwards environment is automatically created. This is implemented as a custom cookie, with the name JSESSIONID. This will probably be suitable for your JD Edwards environment. However, depending on the configuration of your environment, you may need to modify it. In addition, to enable RUEI to monitor and track users over the complete session, ensure the cookie path is set to "/".

Verifying the Cookie Configuration

To verify your cookie configuration, do the following:

Clear all cookies in the browser.
(Re)login to the JD Edwards application.
View a few pages in JD Edwards.
Logout.
Wait for at least 10 minutes.
Open the RUEI Reporter environment.
Select Browse data, open the All sessions group, select Session diagnostics, and locate the recorded session (by user ID or time). You can filter on applications.
Open the session and verify that:
- There are more page views reported than just the login. This verifies the session ID is preserved after the login.
- At least some JD Edwards application activity has been recorded.

When not all hits are connected with the same cookie (these are reported as anonymous pages), it is recommended you investigate where the problem is located, and resolve it in the appropriate manner. For example, the domain or path option of the cookie.

N.6 Hostnames and URL Prefixes

A JD Edwards Implementation, and the JD Edwards instance, can be identified with a hostname. Generally, a JD Edwards suite can be accessed in two ways: using only the hostname, or using the fully-qualified hostname (including the domain). Generally, you only need to specify the domain.

Table N-2 shows how an application's dimensions are reported in RUEI.

Table N-1 JD Edwards Suite Definitions Mapping

Dimension level	Content
Application.name	`productname (suite_name)`
Application. page-group	`suite_name.productcode » application name`
Application.page-name	`suite_name.productcode » application code » formname.action`

where:

application code is the code of the JD Edwards application used by the user. For example, the application code for "sales order entry" is p4210. formname is the name of the JD Edwards form used. For example, the form W01012b has the name "work with addresses".
application name is the name of the JD Edwards application used by the user. For example, the application name for p4210 is "sales order entry".
product code is the code for the JD Edwards product used by an JD Edwards application/form. For example, the address book application (p01012) is part of the JD Edwards product "addressbook" which has product code 01. In JD Edwards, this is sometimes referred to as "system code".
product name is the name for the JD Edwards product used by an JD Edwards application/form. For example, the address book application (p01012) is part of the JD Edwards product "addressbook" (product code 01).

Figure N-1 shows an example of how a JD Edwards application is reported in RUEI.

Figure N-1 Example of JD Edwards Application Page Name Reporting

Description of "Figure N-1 Example of JD Edwards Application Page Name Reporting"

N.7 Verifying and Evaluating Your Configuration

To ensure the quality of the data being collected and reported by RUEI for your JD Edwards-based applications, it is strongly recommended you verify their reported details. You should pay particular attention to the number of associated pages detected for the defined suite(s).

Select Browse data, then select the All pages group, and then the Applications sub-group. Within the individual dimensions, such as Page views and hits, you can see page views are reported for several applications. The suite name in the definition is shown between brackets. An example is shown in Figure N-2.

Figure N-2 Example JD Edwards Page Views

Description of "Figure N-2 Example JD Edwards Page Views"

Note:

The unique pages identified counter and the Last page identified indicator (shown in Figure 6-47) are disabled. Similarly, the manual page naming facility is not available.

N.8 Data Items

The JD Edwards-specific data items shown in Table N-2 are reported by RUEI.

Table N-2 Dimensions

Item	Description
JD Edwards suite/Code	The code of a JD Edwards suite, as defined in its configuration definition. This data makes it possible to distinguish between different monitored JD Edwards suites.
JD Edwards suite/Name	The name of a JD Edwards suite, as defined in its configuration definition. This data makes it possible to distinguish between different monitored JD Edwards suites.
JD Edwards form/ID	The ID of the JD Edwards form used. The JD Edwards form name is based on the form code (W...) and the JD Edwards database configuration. This makes it possible to distinguish between the different forms monitored during sessions.
JD Edwards form/Name	The name of the JD Edwards form used. The JD Edwards form name is based on the form code (W...) and the JD Edwards database configuration. This makes it possible to distinguish between the different forms monitored during sessions.
JD Edwards action/ID	In forms/applications, people perform actions. These actions are monitored and reported here. (Note that most JD Edwards actions are encoded).
JD Edwards action/Name	In forms/applications, people perform actions. These actions are monitored and reported here. (Note that most JD Edwards actions are encoded).
JD Edwards application/ID	The ID of the JD Edwards application used. The JD Edwards application name is based on the application code (P...) and the JDE database configuration. This makes it possible to distinguish between the different applications monitored during sessions.
JD Edwards application/Name	The name of the JD Edwards application used. The JD Edwards application name is based on the application code (P...) and the JDE database configuration. This makes it possible to distinguish between the different applications monitored during sessions.
JD Edwards application version/ID	The ID of the JD Edwards application version used.
JD Edwards application version/Name	The ID of the JD Edwards application version used.
JD Edwards environment/Name	The environment selected when the user logged into JD Edwards.
JD Edwards product/Code	The code of the JD Edwards product used. JD Edwards applications are part of a product which is shown here. JD Edwards products are sometimes referred to by their system code or product code.
JD Edwards product/Name	The name of the JD Edwards product used. JD Edwards applications are part of a product which is shown here. JD Edwards products are sometimes referred to by system code or product code.

N.9 Known Limitations

Currently, the Oracle Real User Experience Insight accelerator for JD Edwards does not work with all JD Edwards functionality. In particular, the following known limitations exist:

Reporting is based on the last activated area. Hence, when an end user is browsing simultaneously in multiple browser windows, the reported page name may contain incorrect information.
Currently, the create_JDE_info.sh script only runs on Unix JD Edwards servers.
An error is not immediately reported if an invalid connect string is specified when running the create_JDE_info.sh script. You will need to press Enter several times before the error is reported.
When users start multiple applications simultaneously, the load and server time for the application start page is sometimes incorrectly booked on one of the started applications.

Footnote Legend

Footnote 1: The script can also be run in the acceptance environment if it is equivalent to the production environment.