The JD Edwards Deployment Server configures and distributes software packages across enterprise environments. This guide explains what a JDE Deployment Server is and its importance in the enterprise technology landscape and provides step-by-step instructions for installation and management.
Key Takeaways
- The JD Edwards Deployment Server is essential for managing software deployments and configurations across JD Edwards environments. It requires specific hardware and administrative settings for proper installation.
- Preparing for installation involves ensuring all prerequisites such as disk space, administrative privileges, and downloading the necessary installation images to avoid future conflicts.
- Ongoing management of the Deployment Server includes monitoring performance, maintaining software updates, and using specific tools to handle database connectivity and troubleshooting effectively.
Understanding the JDE Deployment Server
The JD Edwards Deployment Server is critical in managing enterprise server installations and application deployment. It integrates various components of the JD Edwards architecture to ensure that software packages are correctly configured and distributed across different environments, including the security server. It offers a flexible and accessible solution for many enterprises and associated technology solutions, including the DEP server.
Since Release 9.1, only the Oracle Enterprise Edition (OEE) database is supported for the Deployment Server. Installation can also occur in a virtual machine, offering additional deployment options and flexibility. A key function of the Deployment Server is managing objects within the JD Edwards environment, which reside in the file system and are essential to the server’s operation.
The components of the JD Edwards architecture are often logical rather than strictly physical, allowing for a more flexible deployment. This setup means that various components can share hardware resources, optimizing the use of physical infrastructure. Specifying an intuitive Oracle Home name is also crucial, as it facilitates easier navigation and usage.
Prerequisites for Deployment Server Installation
All prerequisites must be met before installing the deployment server. The JD Edwards EnterpriseOne Deployment Server should be installed on a Microsoft Windows machine, preferably on an Intel Pentium-based system. All JD Edwards EnterpriseOne processes on Windows 2008 must be executed with Administrator privileges to prevent random failures.
A minimum of 15 GB of free disk space is required to install the Deployment Server image, and another 15 GB is needed to create the parent download directory for the install image. Additionally, the C: drive must have sufficient space to accommodate temporary files generated during the installation process.
Installing the Visual Studio 2008 SP1 Runtime is necessary before beginning the Deployment Server installation. These runtime libraries, available from the Microsoft Download Center, are used by EnterpriseOne Tools and EnterpriseOne Applications. Additionally, shutting down all running programs that could cause DLL conflicts is crucial before running the installation program.
Preparing for Deployment Server Installation
Preparation is key to a successful deployment server installation. The JD Edwards Deployment Server facilitates deploying JD Edwards EnterpriseOne applications, managing configurations, and handling software distribution across environments. Ensuring all prerequisites are in place, such as specific hardware requirements, supported Windows versions, required disk space, and administrative permissions, sets the foundation for a smooth installation process.
Preparatory steps include downloading the deployment server install image and setting up the installation directory. These tasks help ensure the installation proceeds without any issues and that the Deployment Server functions optimally once installed.
Downloading the Deployment Server Install Image
To install the Deployment Server image successfully, download the source DVD images into a designated directory with at least 15 GB of available space. This space ensures that all installation components can be accommodated. Use tools like 7-Zip or WinZip to unzip the DVD images to avoid incomplete extraction issues.
After unzipping, verify the integrity of the files. Check the SPEC_MASTER.DBF file, which should be 1.8 GB in size, to confirm successful extraction. Ensure all files follow the same structure as the Disk1DeploymentServer directory. This step helps prevent file structure issues that could later cause installation errors.
Setting Up the Installation Directory
Next, create the necessary directories for installation by expanding all disk images under a common directory called Disk1. Before making any changes to the InstallManager.htm file, save a copy of the original for backup purposes. Using Notepad.exe for editing the InstallManager.htm file is advisable.
This setup ensures that the installation directory is well-organized and allows for reverting any modifications to installation files if necessary. Proper directory setup is crucial for a smooth and error-free installation process.
Installing the Deployment Server
After completing the preparation, proceed to install the Deployment Server. This process involves several steps, including running the InstallManager.exe, configuring installation paths, and completing the installation. Each step must be executed precisely to ensure a successful deployment.
Running the installation as an administrator helps prevent unpredictable failures during JD Edwards EnterpriseOne processes on Windows 2008. It is also recommended that the JD Edwards EnterpriseOne Deployment Server use IPv4.
Running InstallManager.exe
To initiate the JD Edwards EnterpriseOne Deployment Server installation, locate Disk 1 or an equivalent installation image. Start the installation process by executing InstallManager.exe from the installation media. Based on your preferences, select the appropriate installation type, either ‘Custom‘ or ‘Typical‘.
InstallManager.exe reads the InstallManager.htm file to display available options and guide you through installation. This executable is the primary tool for initiating and managing the installation, ensuring all program files and Windows Explorer are correctly set up.
Configuring Installation Paths
During the installation, specify the Oracle Home path and a name for that path on the ‘Specify Home Details’ screen. The Oracle Home directory must include all files related to an Oracle product during the JD Edwards installation. Configuring an intuitive name for the Oracle Home can simplify future navigation and installation management.
You will also need to specify the directory path and names of the JDBC driver files during the Deployment Server installation. Correctly configuring these paths ensures the server can access all necessary files and function correctly.
Completing the Installation
As the installation progresses, you may encounter security warnings. To proceed, confirm the action by clicking the ‘Run‘ button. After installing the Deployment Server, run the TLOVM913 Tools Accelerator to enable service functionalities.
These steps ensure the Deployment Server is fully operational and ready to manage JD Edwards EnterpriseOne applications and configurations.
Working with JDBC Drivers on the Deployment Server
The JD Edwards Deployment Server relies on JDBC drivers for database connectivity. These drivers ensure seamless communication between the Deployment Server and the database server. JDBC driver files should be placed in a specific directory on the Deployment Server, typically under Misc in the Deployment Server installation path.
Managing these drivers involves obtaining the correct ones and placing them in the designated directories. This process is vital for maintaining a stable and functional deployment environment.
Obtaining JDBC Drivers
JDBC drivers must be sourced from the database vendors, such as the Oracle Technology Network, with the necessary Oracle support. Ensure that the JDBC drivers obtained are compatible with the current version of JD Edwards EnterpriseOne. Compatibility is crucial to prevent connectivity issues and ensure smooth operation.
Copying JDBC Drivers to the Deployment Server
Copy JDBC drivers before running OUI. During the Deployment Server installation, provide a directory location and name for the JDBC drivers. To prevent conflicts, avoid having multiple Oracle JDBC driver files in the same folder. Proper placement of these drivers ensures they are readily accessible for database connectivity.
Setting Up the Local Oracle Database
Setting up the local Oracle database is a critical step in deploying the JD Edwards Deployment Server.
Before installation, a Microsoft Visual C++ compiler must be installed on the Deployment Server. Due to the need for temporary space, the disk space required for JD Edwards EnterpriseOne should be three times the base requirement. Additionally, a 32-bit Oracle database client must be installed to enable access to a local OEE database for the Deployment Server.
Proper setup ensures the Deployment Server can effectively manage and interact with the local database, facilitating smooth operation and management of JD Edwards EnterpriseOne applications.
Installing the Local Oracle Database Client
Initiate the local database installation using InstallManager.exe. The version of the Oracle Enterprise Edition (OEE) database included with the Deployment Server installer is 11gR2. During the installation process, specify a global database name and an Oracle system identifier.
Installing the local Oracle Database client adds the bin directory to the Windows PATH. Configure the PATH variable so that the 32-bit client path comes before any 64-bit database path. The default installation path for the local Oracle database is C:OracleE1Local, and the local database established after installation is named E1Local.
The installation provides SQLPlus.exe and SQL Developer as database tools. After installing the database client, copy the tnsnames.ora file to a subdirectory under the database client installation directory.
Configuring the Local Database
Set the PATH so the 32-bit client path comes before the 64-bit client path. The default password used by administrative database scripts is ‘Admin,’ and the default path for the local Oracle database installation is C:OracleE1Local.
If changing the password fails, stop and restart the OracleServiceE1LOCAL and OracleE1LocalTNSListener database services.
Managing the Deployment Server
Effective management of the Deployment Server is essential for maintaining system stability and performance. It is crucial for managing updates across distributed instances of software components. Deployment issues can arise due to slow boot times affecting service startup.
Checking the Process ID in Process Explorer helps identify processes that may be causing conflicts. Management involves using specific tools and following best practices to ensure efficient and reliable server manager operation.
Using EnterpriseOne Application P96717
The EnterpriseOne application P96717 is designed to manage tablespaces in the JD Edwards database. To ensure proper script execution, open the command prompt with administrative privileges. Edit the JDEdwardsE910 Planner Data file to prepare the export tablespace script.
Navigate to the JDEdwardsE910 Planner Data directory to prepare for importing tablespaces. Comment out any lines in the script associated with tablespaces you do not intend to import. Run the export tablespace script as an administrator by executing it in the command prompt.
Comment out tablespaces not meant for import in the ‘Attach Planner‘ file before execution. Use the ‘CD’ command in the command prompt to change to the directory where the batch files are located.
Best Practices for Performance
For optimal performance, it’s recommended that the deployment server’s hard drive maintains at least 20% free space. Insufficient free disk space can lead to degraded performance and potential operational issues on the JD Edwards EnterpriseOne system. Regularly monitoring disk space and ensuring it remains within optimal levels is crucial for maintaining server performance.
Maintaining optimal performance for the JD Edwards Deployment Server is crucial for efficient operation and reliability. This involves not only managing disk space but also regularly updating software and monitoring system health to preemptively address any issues that could impact performance.
Updating and Maintaining Your Deployment Server
Keeping your Deployment Server up-to-date ensures it runs smoothly and securely over time. After installing the Deployment Server, you must run the TLOVM913 Tools Accelerator to enable service functionalities. Failure to do so means services cannot be started, which could significantly impair the server’s functionality.
The Oracle Home path must remain the same value you specified during installation. Consistency in these configurations helps maintain the integrity and functionality of the Deployment Server over time.
Installing the Latest Tools Release
The recommended software updates for the Deployment Server include the Latest Planner Update, Tools Release, and Tools Release Patch.
Change Assistant is the preferred tool for obtaining the latest software updates for the deployment server. You can download various updates using Change Assistant, including the Latest Tools Release, Tools Release Patch, and Planner Update ESU from the JD Edwards EnterpriseOne Update Center.
To install the latest Tools Release Patch on the Deployment Server, download it from the Update Center and follow the Tools Release documentation to deploy packages. Keeping the Tools Release updated ensures that your Deployment Server has the latest features and security improvements.
Running Planner Updates
A valid JD Edwards EnterpriseOne user account is necessary to initiate the Planner installation process. You can confirm the successful installation of the planner update by viewing the JD Edwards EnterpriseOne Deployment Server Setup form.
Regularly running planner updates helps keep the server’s planners in sync with the latest configurations.
Troubleshooting Common Issues
Even with meticulous preparation and installation, issues can arise. Common problems include performance degradation due to incorrect case usage in the E1Local configuration, which can decrease the performance of JD Edwards EnterpriseOne. Additionally, OEE logs are available for the Deployment Server to help diagnose installation problems.
The Deployment Server must be rebooted after installing or uninstalling the local Oracle database. This ensures that any configuration changes take effect and the server operates correctly.
Checking Installer Logs
To locate a locked directory, follow these steps:
- Input the full name of the directory in Process Explorer.
- Utilize Process Explorer to determine which process has a directory locked, allowing for effective troubleshooting.
- If the Oracle listener service is not running, check if it may be due to a slow boot-up of the machine.
If a file in the E1Local directory is locked, stopping the OracleServiceE1LOCAL service may resolve the issue. Changing a service to manual startup may be necessary if a process continues to lock a file after rebooting. Checking the installer log file is essential for diagnosing installation problems effectively.
Resolving Configuration File Issues
Encrypting the password is necessary to enable database access for proper security and functionality. If the database password was decrypted using ReconfigureMSDE, re-encrypt it. If an invalid username/password error occurs, verify that the E1Local database system account password is valid.
The jdbj.ini file specifies the location of the tnsnames.ora file, which is critical for database connectivity. Uncommenting unused database drivers in configuration files can help streamline the deployment process.
The Oracle Listener Service may not start due to the machine’s slow bootup. If the Jde.log indicates ORA-12541, it shows that the Oracle Listener Service is not running.
Adding Additional Environments
The installer must be executed again using the original disk image to incorporate a new environment not included in the initial installation.
The OUI-based installer cannot be used to add additional environments; the original installer must be utilized. The Path Code Master (F98611) is essential for managing deployment server configurations and supporting operations.
Adding new environments ensures that your Deployment Server can handle multiple configurations and requirements, enhancing its versatility and utility.
How Can We Help?
Whether you need help assessing your current JDE system setup, additional support managing complex data migration from JDE World to EnterpriseOne, or an extra hand facilitating effective integrations between JDE and other enterprise applications, Surety Systems is here to help.
Our senior-level JD Edwards consultants have the skills and experience to handle your critical project needs and ensure your internal teams are prepared for continuous improvement and innovation.
For more information about our JD Edwards consulting services or to get started on a project with our team of expert consultants, contact us today.
Frequently Asked Questions
What are the prerequisites for installing the JD Edwards Deployment Server?
To install the JD Edwards Deployment Server, ensure you use a Microsoft Windows machine with at least 15 GB of free disk space, have administrative privileges, and have the Visual Studio 2008 SP1 Runtime installed.
How do I obtain and verify the Deployment Server install image?
To obtain and verify the Deployment Server install image, download the source DVD images into a designated directory with at least 15 GB of space, then use tools like 7-Zip or WinZip to unzip them. It is crucial to verify the file SPEC_MASTER.DBF to confirm successful extraction.
What should I do if I encounter security warnings during the installation?
If you encounter security warnings during installation, confirm the action by clicking the ‘Run‘ button to proceed. This will allow the installation to continue without interruptions.
How can I manage JDBC drivers on the Deployment Server?
To manage JDBC drivers on the Deployment Server, ensure you obtain compatible drivers from the database vendor and copy them to the specified directory on the server. This process is crucial for successfully integrating your JD Edwards EnterpriseOne version.
What steps should I take if the Oracle Listener Service is not running?
If the Oracle Listener Service is not running, verify its status and check for any delays during system startup. You may also use Process Explorer to identify locked files and adjust the service startup settings.