6 Working with JD Edwards EnterpriseOne on Windows Terminal Server

This chapter contains the following topics:

6.1 Understanding Windows Terminal Server

Windows Terminal Server (WTS) provides an excellent solution for Oracle's JD Edwards EnterpriseOne in a WAN environment. WTS enables you to set up multiple terminal server client machines that need only contain the WTS client software. You can use less powerful machines to function as terminal server clients. These clients connect to a machine set up with TSE software. Multiple users can simultaneously connect to the same terminal server to run JD Edwards EnterpriseOne.

Windows Terminal Server (WTS) is a multi-user extension to the Microsoft Windows family of operating systems. WTS enables users to share an application that resides on the terminal server. The terminal server performs all the processing for an application, and then sends a picture of the screen to the client terminal. Only keystrokes and mouse movement occur at the terminal. These movement commands travel through the network to the server, which returns the modified screen to the terminal.

This list provides an example of the WTS process flow:

  • Step 1: JD Edwards EnterpriseOne client applications execute on terminal server.

  • Step 2: The terminal server sends the video for the user interface across any connection.

  • Step 3: The terminal server client displays the user interface.

  • Step 4: The terminal server client sends keystrokes, mouse clicks and screen shots back to the terminal server where processing occurs.

By sending only the information necessary to recreate the screen and convey mouse and keyboard events, TSE provides LAN-like performance over WAN and dialed connections.

TSE enables you to set up multiple users to work with a single client installation of JD Edwards EnterpriseOne. By sharing a single copy of JD Edwards EnterpriseOne on the terminal server, you reduce the costs of deployment and administration.


Sun-Solaris can be added to the list of enterprise servers that can run in a JD Edwards EnterpriseOne configuration with a terminal server.

6.1.1 Incorporating Citrix MetaFrame with WTS

WTS provides multi-user technology that uses a presentation protocol called Remote Desktop Protocol (RDP). RDP, based on the International Telecommunications Union T.120 protocol, is a viable option if you plan to use only Win16/Win32 clients in an uncomplicated configuration.

If the network comprises multiple platforms and requires optimum performance, Citrix offers a product called Citrix MetaFrame with multi-user technology that provides additional functionality to WTS, such as load-balancing and the support of more client platforms. MetaFrame uses the Independent Computing Architecture (ICA) presentation protocol on which Citrix based WinFrame, a successful multi-user product for Windows 3.51.


If you start JD Edwards EnterpriseOne as a specified application through ICA, you cannot view the jde.ini, jde.log, and jdedebug.log files.

This table lists the capabilities of WTS RDP and MetaFrame:

Capability TSE RDP MetaFrame
Client Platforms WTS client software runs on these platforms:
  • Windows 16-bit

  • Windows 32-bit

  • Some RDP-equipped Windows terminals

  • Windows CE

MetaFrame runs on these platforms:
  • DOS

  • Windows 16-bit

  • Windows 32-bit

  • X-Term

  • MacIntosh

  • Solaris

  • Windows CE

  • Some ICA-equipped network computers

  • Some internet browsers as a plug-in

Network Topologies WTS RDP supports the TCP/IP standard. MetaFrame supports these standards:
  • IPX

  • SPX

  • PPP

  • NetBIOS

Load-balancing Windows supports load balancing. You can purchase an option for MetaFrame that provides load-balancing capabilities.
Encryption N/A You can purchase an option for MetaFrame that provides the encryption of ICA traffic.
CCPDD:cut/copy/paste/drag/drop Windows 2000 supports cut, copy, paste, drag, and drop. MetaFrame enables CCPDD between the session window and the underlying Windows desktop.
Device Mapping WTS RDP enables you to map local devices for printing through a work-around. MetaFrame enables you to map devices local to the WTS client from the terminal server. For example, you can locally map hard drives, fax modems, and printers.
Session Shadowing Windows supports remote control. With MetaFrame loaded, WTS supports an administration tool called session shadowing. Session shadowing helps administrators audit remote sessions. You might also use session shadowing for video conferencing and in a support desk role.

6.1.2 WTS Restrictions in Multi-user Mode

JD Edwards EnterpriseOne is WTS-aware. WTS-aware means that when you deploy JD Edwards EnterpriseOne as a client on a terminal server, the software automatically recognizes the terminal server and configures itself to run in multi-user mode. Because of the configuration required by multi-user mode, these restrictions apply to terminal server users:

  • Disabled development with Form Design Aid, Report Design Aid, and Table Design Aid, including Object Management Workbench check-in and check-out capabilities.


    The restriction on development does not prevent new versions of existing applications, but only the modification of current applications and the creation of new applications. Also, a complete set of development specifications (500+ MB) defeats the purpose of a thin client.
  • Disabled local processing for batch applications.

    All batch applications process on a separate batch server to avoid an impact to performance on the terminal server.

  • Disabled Just-In-Time-Installation (JITI).

    Because you deploy a full client package to the terminal server, JITI is not recommended.

  • Disabled intensive specification file access.

    Applications that intensively access specification files, such as the Universal Table Browser application, are not active due to the strain put on the terminal server when the application retrieves data. Also, file level locking could prevent access to data in the specification files for other users.

A standard JD Edwards EnterpriseOne configuration and a terminal server configuration are not mutually exclusive within an enterprise. You can mix a standard configuration with a terminal server configuration to maximize the overall performance. For example, you can use a standard JD Edwards EnterpriseOne configuration over a LAN, and use a terminal server configuration to support remote sites across a WAN.

6.1.3 Network Considerations

The terminal server must reside on the same local area network (LAN) as the enterprise server or database server, or both. Include one normal JD Edwards EnterpriseOne client on the LAN to verify performance and function. Normal JD Edwards EnterpriseOne LAN requirements apply.

For a wide area network (WAN), you must use a 56KB, or faster, line.

6.1.4 Performance Considerations

When you add any ICA session, change the Window Colors display properties to 16 color mode or to the lowest setting that the software and hardware allow. You can access display properties from the Control Panel.

Also, for the Citrix setup, you need to select the Compress data stream and Cache bitmaps to disk options. See the appropriate Citrix documentation for more information about how to modify these settings.

6.2 Setting Up JD Edwards EnterpriseOne on the Terminal Server

Because JD Edwards EnterpriseOne is WTS-aware, running on a terminal server is almost identical to running a standard client.

When performing certain processes, such as creating log files and running UBEs, JD Edwards EnterpriseOne checks whether it resides on a terminal server or standard client. If it detects a terminal server, the software automatically switches to multi-user mode.

In multi-user mode, JD Edwards EnterpriseOne processes data while simultaneously protecting data integrity and maintaining performance on the terminal server. Multi-user mode also masks any of the multi-user activity from a user so that a terminal server session of JD Edwards EnterpriseOne looks no different than a standard JD Edwards EnterpriseOne client session.

See Also:

  • JD Edwards EnterpriseOne Hardware and Software Requirements Guide.

6.2.1 Setting Up JD Edwards EnterpriseOne on the Terminal Server

To set up JD Edwards EnterpriseOne on the terminal server:

  1. Install Windows Terminal Server on the machine that you will use as the terminal server.

    Refer to the Microsoft documentation for information about how to set up Windows Terminal Server software.

  2. Install Microsoft Terminal Server Client software onto the machines that you will use as terminal server clients.

    You can connect to the terminal server from the Terminal Server Client option on the Programs menu. This file also resides in the Terminal Server Client subdirectory in the Program Files directory. Refer to Microsoft documentation for information about how to set up Terminal Server Client software.

  3. Depending on the type of database you use, you might need to install software so that the client can properly connect with the server where the database resides.


    You must use Add/Remove Programs on the Control Panel to install applications on the terminal server. During installation, make sure that you select the All users begin with common application settings option on the Change User Option dialog box.

    Install these software packages on the terminal server as necessary:

    • Oracle for Windows

    • SQL Server client

    • Client Access

    • DB2 for IBM i Connect

  4. Install a full package of JD Edwards EnterpriseOne. You need to install a full package because JD Edwards EnterpriseOne on the terminal server is multi-user. If you install a partial package, multiple users will simultaneously experience Just-In-Time-Installation, which will negatively affect performance on the terminal server.


    Install JD Edwards EnterpriseOne from the WTS console or use a third-party remote administration software. Do not install through a remote desktop connection. Use Add/Remove Programs on the Control Panel to install JD Edwards EnterpriseOne on the terminal server. During installation, make sure that you select the "All users begin with common application settings" option on the Change User Option dialog box.

After you perform these steps, you should be able to successfully run JD Edwards EnterpriseOne from terminal server client machines.

6.3 Troubleshooting JD Edwards EnterpriseOne on Windows Terminal Server

This section discusses how to:

  • Troubleshoot UBE output security on WTS.

  • Submit a UBE locally and run it on the WTS.

  • Troubleshoot import/export with Microsoft Excel.

  • Troubleshoot specification files are locked.

  • Reduce JITI frequency.

  • Troubleshoot user cannot restart JD Edwards EnterpriseOne.

  • Troubleshoot logging off versus disconnecting.

  • Troubleshoot shortcuts do not work in email messages.

  • Troubleshoot data selection and sequencing criteria lost.

  • Troubleshoot run-time error occurs during server connection test.

  • Troubleshoot JD Edwards EnterpriseOne development tools are disabled.

  • Troubleshoot users experience problems accessing JD Edwards EnterpriseOne.

  • Troubleshoot log path is incorrect.

  • Troubleshoot shortcut path is incorrect.

  • Troubleshoot only one user can log in to JD Edwards EnterpriseOne.

6.3.1 Troubleshooting UBE Output Security on WTS

A JD Edwards EnterpriseOne WTS user sends PDF files by default from the enterprise server to the local \E900\PrintQueue directories using the Work With Servers (P986116) application. Users select View PDF from the Row menu of the Submitted Job Search form. Because the files are saved to a user's local PrintQueue directory, another user can view the PDF file in Windows Explorer or in Adobe Acrobat.

You can relocate the PrintQueue directory by adding this section to the jde.ini file:


Server administrators need to make the jde.ini file modification of each user on each WTS so that the PDF output points to each individual user profile directory. With the PrintQueue directory located in the user profiles directory, the PDF files are protected by Windows security. Only server and system administrators have access to the files.

6.3.2 Submitting a UBE Locally and Running it on the WTS

You cannot locally submit UBEs to run on the WTS because of resource constraints such as CPU power. You can run UBEs on a dedicated WTS or during hours when no other JD Edwards EnterpriseOne users are using the machine. Complete the task to submit a UBE locally and run it on the WTS.

To submit a UBE locally and run it on the WTS:

  1. From the System Administration Tools menu (GH9011), select Logical Data Sources (P986115).

  2. On Logical Data Sources, select the WTS machine name with System as the data source and click Select.

  3. On Work with Data Sources, click Add.

  4. On Data Source Revisions, complete these fields:

    • Data Source User

      Enter DB to specify a Local Data Source.

    • Data Source Name

      Enter WTS Local.

    • Data Source Type Enter N to specify MSDE/ODBC.

      Enter E to spicify OEE.

    • DLL Name

      Enter JDBODBC.DLL.

    • Database Name

      Enter System Local.

    • Server Name

      Enter LOCAL.

    • Platform

      Enter LOCAL.

  5. When you run the UBE on the WTS, on the Work with Batch Versions from, select the report you want to run and click Select.

  6. On Version Prompting, select Advanced from the Form menu.

  7. On Advanced Version Prompting, select the Override Location option and click OK.

  8. On Version Prompting, select the Data Selection option and click Submit.

  9. On JDE Data Sources, select WTS Local as the data source and click Select.

6.3.3 Troubleshooting: Import/Export with Microsoft Excel

Importing a Microsoft Excel spreadsheet into a JD Edwards EnterpriseOne grid intermittently fails when users are running WTS.

Please check the MTR (minimum technical requirements) to be sure you are running the latest supported versions of Microsoft Office. You install a single of Microsoft Office 2000 on the WTS. Multiple users then connect to the server and run Microsoft office from the server.

6.3.4 Troubleshooting: Specification Files are Locked

In these circumstances, JD Edwards EnterpriseOne users get a message box to indicate that a specification file is currently unavailable:

  • When another JD Edwards EnterpriseOne session on the same WTS machine performs a data dictionary Just-In-Time-Installation (JITI).

  • When another JD Edwards EnterpriseOne session receives a WTS run-time error dialog box. Generally, this type of error occurs when a memory violation occurs.

In both cases, the specification file or files are locked. The specification files will be unlocked when either the WTS completes the JITI process or a user closes the WTS run-time error dialog box.

To prevent the specification files from being locked when JD Edwards EnterpriseOne performs a JITI, reduce the frequency that JD Edwards EnterpriseOne performs JITIs. Complete this task:

6.3.5 Reducing JITI Frequency

To reduce JITI frequency (B73.3.1, B73.3.2, and B73.3.3):

  1. Run the Generate global table spec (R98CRTGL) batch application on a non-WTS JD Edwards EnterpriseOne client to generate full GLBLTBL specification files.

  2. Copy the full glbltbl.ddb and glbltbl.xdb to the WTS machines.

6.3.6 Troubleshooting: User Cannot Restart JD Edwards EnterpriseOne

Occasionally, when a memory violation occurs in a JD Edwards EnterpriseOne WTS session, the terminal server prevents the user from restarting JD Edwards EnterpriseOne. The administrator must then sign onto the terminal server and end the OEXPLORER.exe process from the Task Manager. After the administrator ends the process, the user can sign on to JD Edwards EnterpriseOne again.

When a run-time exception occurs, JD Edwards EnterpriseOne should immediately exit. To instruct JD Edwards EnterpriseOne to immediately exit in this situation, change the EXCEPTION_Enabled setting in the jde.ini to False:


6.3.7 Troubleshooting: Logging Off Versus Disconnecting

Users should always log off their WTS session rather than disconnecting. Logging off shuts down all processes completely for the user.

6.3.8 Troubleshooting: Shortcuts Do Not Work in Email Messages

Workflow provides the ability to send shortcuts to JD Edwards EnterpriseOne applications using email messages. This function does not work when the email application, such as Microsoft Outlook, is not currently active on the terminal server. When the email application invokes the shortcut, the operating system attempts to launch the shortcut on the local machine and not on the terminal server.

Run the email application and JD Edwards EnterpriseOne on the same terminal server machine.

6.3.9 Troubleshooting: Data Selection and Sequencing Criteria Lost

This situation occurs when two or more users are signed on to the same terminal server using the same pathcode.

The first user submits a batch application from Batch Versions, changes the data selection criteria, and then stops at the printer screen. The second user then goes into Batch Versions to submit the same version of the batch application, changes the data selection criteria, and then stops at the printer screen. When the users click OK to send the batch application to the enterprise server for processing, the data selection criteria for the second user overrides the selection criteria for the first user.

A modification to batch processing in JD Edwards EnterpriseOne now saves data selection and sequencing criteria in memory rather than in specification files.

6.3.10 Troubleshooting: Run-Time Error Occurs During Server Connection Test

The Server Administration Workbench (SAW) application receives a run-time error when it performs a server connection test. This situation occurs when the user who performs the connection test does not possess the authority to access the pinging mechanism on the target machine.

6.3.11 Troubleshooting: JD Edwards EnterpriseOne Development Tools Are Disabled

JD Edwards EnterpriseOne development tools are disabled on the terminal server. Currently, we instruct customers to perform all development on non-WTS machines.

6.3.12 Troubleshooting: Users Experience Problems Accessing JD Edwards EnterpriseOne

Only administrators can run JD Edwards EnterpriseOne. This situation is a result of the way JD Edwards EnterpriseOne was installed on the terminal server.

As the Administrator, you should use the Add/Remove Programs application on the Control Panel to install JD Edwards EnterpriseOne on the terminal server. During installation, make sure that you select the All users begin with common application settings option on the Change User Option dialog box. This option ensures that the terminal server maintains JD Edwards EnterpriseOne specific files, such as the jde.ini file, across user profiles.

6.3.13 Troubleshooting: Log Path is Incorrect

The log path in the jde.ini for individual users is incorrect.

The JD Edwards EnterpriseOne installation program sets the WTSLogs setting to False. Users should change this setting to True after the installation and before any users run JD Edwards EnterpriseOne.

When the WTSLogs setting is True, the output log directories for each user point to the home directory of the user rather than to the root directory of the drive. The output log directories settings are also defined in the jde.ini file.

6.3.14 Troubleshooting: Only One User Can Sign in to JD Edwards EnterpriseOne

The main JD Edwards EnterpriseOne window fails to appear after entering the password for all other users.

For B73.3.2 with Service Pack 10 or greater, place the JD Edwards EnterpriseOne command line switch /NoLogo, located in the JD Edwards EnterpriseOne shortcuts, on the desktop and on the Start menu if not already present. Separated by a space, append the text to the end of the line in the Target edit box of the shortcut properties window. Do not include the quotation marks. This will prevent the display of the splash screen.