O 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.

O.1 Introduction to JD Edwards

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.

O.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).

O.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 10.1, "Working With Suites".

O.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:

  1. 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.

  2. 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.

  3. Follow the procedure described in Section 10.1.2, "Uploading Configuration Files" to upload the generated files to the Reporter System.

O.4.1 Creating the Info Files Manually

An alternative to running the create_JDE_info.sh script is to create the info files manually. This requires System I Navigator (iseries Navigator for windows). To create the files:

  1. Open iSeries Navigator in Windows.

  2. Select the appropriate Databases\schema branch inside iSeries Navigator.

  3. Create temporary views to export the data.

    1. Click Run a SQL Script in iSeries Naviagator

    2. Run SQL similar to the following:

      CREATE VIEW OL910.F9865_TEMP1 (SWFMNM,SWOBNM) AS SELECT
TRIM(a.SWFMNM),a.SWOBNM FROM OL910.F9865 a;
CREATE VIEW OL910.F9865_TEMP2 (SWFMNM,SWMD) AS SELECT TRIM(a.SWFMNM),a.SWMD
FROM OL910.F9865 a;
CREATE VIEW OL910.F9860_TEMP1 (SIOBNM,SIMD) AS SELECT TRIM(a.SIOBNM),a.SIMD
FROM OL910.F9860 a;
CREATE VIEW DV910.F983051_TEMP (VRPID_VRVERS,VRJD) AS SELECT TRIM(a.VRPID) ||
'__' || TRIM(a.VRVERS), a.VRJD FROM DV910.F983051 a;
CREATE VIEW DD910.F9203_TEMP (FRDTAI,FRDSCA) AS SELECT
TRIM(a.FRDTAI),a.FRDSCA FROM DD910.F9203 a;
CREATE VIEW PRODCTL.F0005_TEMP (DRKY,DRDL01) AS SELECT TRIM(pct.DRKY) ,
pct.DRDL01 FROM PRODCTL.F0005 pct WHERE pct.DRSY like '98 ' AND pct.DRRT
LIKE 'SY' AND pct.DRKY NOT LIKE ' %';
CREATE VIEW PRODCTL.F0005_F9860_TEMP (OBNM,DRDL01) AS SELECT appt.SIOBNM ,
(SELECT pct.DRDL01 FROM PRODCTL.F0005 pct WHERE pct.DRSY like '98 ' AND
pct.DRRT LIKE 'SY' AND pct.DRKY NOT LIKE ' %' AND
TRIM(pct.DRKY)=TRIM(appt.SISY) ) FROM OL910.F9860 appt WHERE appt.SIOBNM
like 'P%' AND appt.SISY NOT LIKE '%55%' AND appt.SISY NOT LIKE '%87%' AND
appt.SISY NOT LIKE '%88%' AND appt.SISY NOT LIKE '%89%' AND appt.SISY NOT
LIKE '%99%';
CREATE VIEW OL910.F9860_TEMP2 (SIOBNM,SISY) AS SELECT
TRIM(appt.SIOBNM),TRIM(appt.SISY) FROM OL910.F9860 appt WHERE appt.SIOBNM
like 'P%' AND appt.SISY NOT LIKE '%55%' AND appt.SISY NOT LIKE '%87%' AND
appt.SISY NOT LIKE '%88%' AND appt.SISY NOT LIKE '%89%' AND appt.SISY NOT
LIKE '%99%';

      In the example above, the schema is named as OL910, PRODCTL, DD910, DV910 etc. Make sure you provide the proper schema name before running the above SQL. Please make sure you replace the schema in the SQL with appropriate schema/library name on your DB2400 install.

      Make sure that the SQL has run successfully before proceeding with the rest of this procedure.

  4. Export the views to a file. For each view you create in step3

    1. Navigate to the view.

    2. Right click on the view name and select Data\Export from the popup menu Use the export wizard to save the data to a file, accepting default options except for the following:

      Use the following filenames for the appropriate view

      F9865_TEMP1 => JDE_formcode2applicationcode.txt
F9865_TEMP2 => JDE_formcode2formname.txt
F9860_TEMP1 => JDE_applicationcode2applicationname.txt
F983051_TEMP => JDE_applicationversioncode2applicationversiondescription.txt
F9203_TEMP => JDE_errorcode2errordescription.txt
F0005_TEMP => JDE_applicationcode2productname.txt
F0005_F9860_TEMP => JDE_applicationcode2productcode.txt
F9860_TEMP2 => JDE_productcode2productname.txt

      Change the String delimiter and choose None and change the Column delimiter and choose None.

  5. Convert all the files from EBCIDIC to UTF-8. For example, using EditPad Lite you can open the files and choose Encoding as EBCIDIC 037: Us & Canada, then choose to Encode the original data with another character set.

  6. Save all the files into a zip file and follow the procedure described in Section 10.1.2, "Uploading Configuration Files" to upload the generated files to the Reporter System.

O.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:

  1. Clear all cookies in the browser.

  2. (Re)login to the JD Edwards application.

  3. View a few pages in JD Edwards.

  4. Logout.

  5. Wait for at least 10 minutes.

  6. Open the RUEI Reporter environment.

  7. 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.

  8. 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.

O.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.

O.7 Data Items

The JD Edwards-specific data items shown in Table O-1 are reported by RUEI.

Table O-1 Dimensions

Item Description

JD Edwards Action

In forms/applications, people perform actions. These actions are monitored and reported here. (Most JD Edwards actions are encoded).

JD Edwards Action Code

In forms/application, people perform actions. These actions are monitored and reported here. (Most JD Edwards actions are encoded).

JD Edwards Application

The name of the JD Edwards application used. The JD Edwards application name is based on the application code (P...) and the JD Edwards database configuration. It makes it possible to distinguish between the different applications monitored during sessions.

JD Edwards Application Code

The ID of the JD Edwards application used. The JD Edwards application name is based on the application code (P...) and the JD Edwards database configuration. It makes it possible to distinguish between the different applications monitored during sessions.

JD Edwards Environment

The environment selected when the user logged into JD Edwards.

JD Edwards Form

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 Form Code

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 Product

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.

JD Edwards Product Code

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.

O.8 Known Limitations

Currently, RUEI 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.

  • Applications that make use of a Rich Internet Application (RIA) framework (such as Ajax) may have reduced replay capability.


Footnote Legend

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