Maintenance Notice - PDF Generation
Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.


Note: Access to static files, including PDF files that are not dynamically generated from our web-based content, is unaffected.

Jump to: navigation, search

Deploying eServices on UNIX Hosts

Configuring and installing eServices on Solaris, AIX, or Linux follows the general procedure introduced in Model Configuration and Installation on Windows. You can use the eServices Configuration Wizards on a Windows host to configure components that will run in UNIX environments.

For the installation phase, however, you should proceed in a slightly different fashion than you would for a Windows-only environment. The main difference is that after configuration, you will need to manually copy the individual component installation packages to each UNIX host, as initially suggested in Model Configuration and Installation on Windows: "Installing eServices Components."

Also consider the guidelines under “Copying Installations to Remote Computers” in the “Genesys Wizards” section of Chapter 4, “Deployment Overview,” of the Framework 8.1 Deployment Guide (the 8.5 Framework Deployment Guide does not discuss configuration wizards).


After you copy the software to the UNIX hosts, do one of the following:

  • Run the setup for individual components manually.
  • Use the eServices CD on each host to run the setup for the components directly from that CD.


Tip
In previous eServices releases, some components required Java Environment and Libraries for eServices and UCS (JELEU), which was supplied as part of eServices. Starting with the 8.5 release, JELEU is no longer required.

Procedure: Deploying eServices on Solaris, AIX, or Linux from a Windows host

Purpose: To suggest how you might use the eServices Configuration Wizards on a Windows host to configure and install components to other hosts for Solaris, AIX, or Linux deployments.

  1. When you run the eServices Configuration Wizard, it will ask you to specify the destination for copying installation packages. Do one of the following:
    • Create a shared directory on your Solaris, AIX, or Linux computer for the installation package deployment, making sure that it is accessible from the Windows host.
    • Create a shared directory on a Windows host (as recommended in Model Configuration and Installation on Windows, in the topic: Create a Shared Directory for the Windows installation), making sure that it is accessible from the Solaris, Linux, or AIX host(s) that will run your eServices components.
      In either case, you must copy all installation packages to the Solaris, Linux, or AIX computer(s) that will host your eServices solution.
  2. On a Windows machine, run the eServices Configuration Wizards as described in Model Configuration and Installation on Windows, in the topic: Model Configuration and Installation on Windows.
    The Wizards copy the installation packages using a directory structure such as the following:
    <Component A>
    		IBM_AIX
    		Linux
    		Solaris
    		Windows_2008
    		
    
    <Component B>
    		IBM_AIX
    		Solaris
    		Windows_2008
    		
    ...
    aix
    		ThirdPartyComponents
    		
    
    linux
    		ThirdPartyComponents
    		
    
    solaris
    		ThirdPartyComponents
    		
    
    windows
    		CommonWizardComponentSet
    		ThirdPartyComponents
  3. After completing configuration using the Wizards, begin installation by running the installation package in platform\ThirdPartyComponents on each host where you plan to install components.
  4. Continue installation by running the installation package for each remaining eServices component. You will find that package in the platform> subdirectory contained in the directory named for each component.
This page was last edited on October 1, 2014, at 12:29.

Feedback

Comment on this article:

blog comments powered by Disqus