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.
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.
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).
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".
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.
Follow the procedure described in Section 10.1.2, "Uploading Configuration Files" to upload the generated files to the Reporter System.
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.
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.
The JD Edwards-specific data items shown in Table O-1 are reported by RUEI.
| 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. |
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.