Professional Documents
Culture Documents
BASE24-es V054 UNIX Install Guide 06-Feb-2006
BASE24-es V054 UNIX Install Guide 06-Feb-2006
GETTING STARTED
GETTING STARTED
1. Preface
a) Pre-Install Checklist and Worksheet
Please ensure you have read and address all the information in the pre-install guide. The
installation automation assumes all entries of the pre-install guide have been addressed and the
install will fail if this is not the case.
b) Example Authorization Scripts
The authorization scripts provided in the auth_example_scripts.zip file are provided as examples
only and should not be considered as “product ready” scripts. There is a readme.txt file in the
auth_example_scripts.zip file that explains each script and its possible use. Refer to the readme
file before using or modifying any of these scripts.
c) BASE24 Product Documentation
A manuals1.zip folder is included. This zip file contains the Publications manuals. Open the zip
file and read the Installing Electronically Distributed ACI Publications <ddMmmyyyy>.pdf
document. This document covers the steps necessary to unzip and load the BASE24
manuals/user guides to the UI Desktop PC. This folder should be extracted to each desktop that
will be running the User Interface.
The source zip files contain source code and are provided for documentation reference purposes
as described in the BASE24-es Customization Guide.
2. Worksheet
a) The BASE24-es UNIX Pre-Install Checklist and Worksheet has already been provided. The
Worksheet should already have been filled out before starting this install.
Use this worksheet to establish the port numbers, paths, and configuration settings to be used
throughout this document to install the ACI desktop user interface, the Version Checker, and the
USEC Server. This worksheet serves as a central location for all site-specific information you
will need to specify when installing the UIF. Numerous steps in this document refer you back to
this worksheet when you need to enter or edit data for site-specific UIF. Make sure that a
worksheet is completed accurately for each system that is being installed, before continuing with
the installation process.
End of Section
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 4
BASE24-es INSTALLATION
BASE24-es INSTALLATION
1. Transfer Folder
a) If software was delivered via the Electronic Distribution method, move all the zip folders from
the distribution location (ED) to a folder on your PC and extract all the zipped folders
received on your shipment to the same folder. Do not extract the folders within these
delivered zipped folders, as the install program will do this for you.
2. List of Zip/Archive Files
a) As part of each shipment of code, there should a file called: report.txt. This file is a report that
ACI generates that describes in detail all the information about your particular shipment.
Open this file and look for the text Archives (near the top of the report). The Archive section
lists all the zip/archive files you should have received for this particular shipment.
Use this information to ensure all the files in the Archive section were sent. Additionally, you
can compare the SDR Product ID’s against your contract Product ID’s.
3. Running ES_INSTALL.exe Program
a) Double click on ES_INSTALL.exe. Refer to the worksheet for your values.
Once all the information has been entered, the desktop will be installed and a number of files
transferred to the target Unix machine for the host installation.
4. Running ESSETUP
a) If you have not installed ICE-XS or c-tree yet, you must do it now prior to the next step. If
you are just now going to install it, the installation files are located in the ES_HOME/install
directory called icexs_product.tar.gz (ICE-XS) and ctree_product.tar.gz (c-tree). Please see
the appropriate Install Guides for installation instructions.
b) To install BASE24-es on your Unix Host Server, from the $ES_HOME/install directory, type
in “./essetup” from the ES_HOME/install directory.
NOTE: The essetup script will need to have executable permission (e.g. chmod u+x essetup).
c) If your Web Application server is WebSphere, and it is located on a different Unix server than
the one on which you ran./essetup, you were then prompted to give your login to FTP the Web
Application configuration files to the WebSphere server. To complete the installation, you
must log in to the WebSphere Unix server and navigate to the ES_HOME/install directory.
NOTE: The essetup script will need to have executable permissions (e.g., chmod u+x
essetup) given again, since permissions are lost when running FTP.
d) The essetup script can be restarted on any given step by including the step as a parameter to
essetup. The step names and the status for each step are listed in the essetup.log file that is
created during execution of essetup.
BASE24-es INSTALLATION
To restart essetup on step 3 (an example):
¾ ./essetup step003
e) You can run the esinfo script that will collect important information pertaining to your new
BASE24-es system in a report form. The report, called “esinfo.log”, is located in $LOGS
directory, will help you become familiar with the directory structure, and all important
configurations. This report is also required documentation for any HELP24 requests. This
report is also appended to the “essetup.log” file. Help24 will also require the “essetup.log” if
any problems with installation.
f) Your c-tree server database has been created with an Administrator User-ID/Password of
ADMIN/ADMIN. This User-ID/Password is encrypted and stored in the secure.set file in
your $CONFIG directory. If you change your User-ID/Password, using the ctadmn utility,
you will need to also recreate this secure.set file with the changes. To do this, please refer to
the Operations Guide in the c-tree utilities/CTCMDSET section.
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 6
¾ . ./env_vars
¾ start_manager.sh
NOTE: Your MQ Manager is automatically started via the “essetup” Installation script.
3. Start c-tree Servers
a) Start your c-tree servers for your BASE24-es system:
¾ ctstart
NOTE: Your c-tree servers were automatically started via the “essetup” Installation script.
4. Start ICE-XS Listeners
a) Reference the ICE-xs Installation Document for information about the ICE-XS startup process.
Use the following command to start the ICE-XS process for each listener:
¾ runicexs xxx_yyy
(where xxx is the System prefix and yyy is the interface name. This “xxx_yyy” is the name of
your ICE-XS NOF file. Example below points to the $ICECFG/ia52_visa.nof file)
example: runicexs ia52_visa
To access your data through the UI, bring up your GUI listener
(i.e., runicexs xxxx_gui).
¾ cd $ES_HOME/ESJMX/bin
¾ runacijmx
NOTE: Your Application Manager is automatically started via the “essetup” Installation script.
6. Start SIS Timer Server Process
a) Start your ES System Timers for your BASE24-es system:
¾ runtimrp
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 7
¾ runis n
¾ runxml
¾ runeopp
NOTE: Perform this step, only if you have purchased the Merchant/POS Acquirer
Interface. Without these modules, the “runcmcp” will fail to run correctly.
¾ runcmcp
¾ runjqbtch
¾ StartVersionChecker
¾ StartUsec
¾ StartES
¾ runjdh n
¾ runifx n
¾ cd $ES_HOME/bin
¾ . ./env_vars
From the WebSphere “bin” directory, run the startup script to start your ESWeb application
server:
¾ startServer.sh ES_<SYSTEM_PREFIX>
Example, if your system prefix was “IA54”, your Application server name is “ES_IA54”, all in
CAPS.
19. Starting the Desktop
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 9
On the workstation where you installed the desktop, perform one of the following:
Or
Access Internet Explorer and enter the following URL address: http://<system IP address or
DNS name>:<port-number>/esweb (e.g., http//172.16.23.61:8004/esweb).
Or
b) The first time you start the ACI desktop application from a workstation, the Version Checker
client window will be displayed. You must press the Update button on this window before you
can access the ACI desktop user interface. This step updates the jar files in the repository on
the workstation and can take several minutes to complete. Once this process has started, do not
interrupt it until it has completed.
c) To log on, click File, Log In. You must change the password and it must be alpha (no
repeating characters) with at least two numerics.
Login Password
SysAdmin SysAdmin01 (default logon/password)
SecAdmin SecAdmin01
TSSSysAdmin TSysAdmin01
TSSAdmin TSAdmin01
WAS: <WAS_DIR>logs/ES_<system_prefix>/SystemOut.log
Java Server: ES_HOME/ESWeb/ESLogs
USEC: ES_HOME/ESUI/Logs/ENTController.log (or .err)
VC: ES_HOME/ESUI/Logs/VerChk*.log (or .err)
xml.exe ES_HOME/logs/<system_prefix>.XML.out
End of Section
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 11
This script will show you the status of your ES system. Below is an example of the output:
¾ esstatus
To continuously refresh, use “esstatusl” to loop every 5 seconds. Use Ctrl-c to break.
¾ esstatusl
A script called runevtparser has been placed into your $BIN directory that allows you to view
your BASE24-es processes Event Messages, using SIEVTQ_XMLPARSER utility. See “Event
Subsystem” section of the Operations Guide for more information on this utility. The
runevtparser defaults to view the current day’s $LOGS/evtlog file.
¾ runevtparser
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 12
¾ runevtparser <evtlog.filename>
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 13
¾ . ./env_vars
¾ stopicexs xxx_yyy
(where xxx is the System prefix and yyy is the interface name)
example: stopicexs ia52_visa
¾ stopis 1
¾ stoptimrp
¾ stopxml
¾ stopeopp
¾ stopcmcp
¾ stopjqbtch
¾ stoprfsh
¾ stopsafm
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 14
¾ stopjdh n
¾ stopifx n
k) Use the following commands to stop the Application Manager (JMX) process:
¾ cd $ES_HOME/ESJMX/bin
¾ stopacijmx
¾ KillESVersionChecker
¾ KillESUSEC
¾ KillES
¾ stopServer.sh ES_<SYSTEM_PREFIX>
¾ ctend
* NOTE: You should shut down all ES processes before shutting down your c-tree
server, since all ES processes have open connections to it.
9. Stop MQ Manager
a) Stop your MQ manager for your BASE24-es system:
¾ stop_manager.sh
* NOTE: You should shut down all ES processes before shutting down your MQ
manager, since all ES processes have open connections to it.
End of Section
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 15
To execute:
¾ cd $ES_HOME/install
¾ chmod u+x esclean
¾ esclean
¾ cd $ES_HOME
The script uninstalls and removes everything that was placed under your $ES_HOME
directory. It will not remove your $ES_HOME directory. An esclean.log will be placed
in your $ES_HOME directory.
NOTE: If your ESWeb was installed onto a different Unix machine, you will need to
run the “esclean” from the $ES_HOME/install directory to remove the ESWeb
application there.
NOTE II: Since $ES_HOME/install directory is deleted during the execution of esclean,
you must change to another directory immediately after the execution of the macro.
End of Section
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 16
Optional Software
1. Installation and Configuration of Application Management
a) Please refer to BASE24-es Application Management Installation and Configuration Guide on
the documents zip folder.
2. Installation and Configuration of MetaMan
b) Please refer to BASE24-es MetaMan Installation and Configuration Guide on the documents
zip folder.
End of Section
ES-CS000-51 Last Modified 02/06/06
BASE24-es (v05.4) UNIX Install Guide Page 17
MODIFICATION HISTORY
MODIFICATION HISTORY
REV DATE INITIALS HISTORY
03/30/05 DMG Initial Release of BASE24-es (v05.2) UNIX Install Guide
04/12/05 JMK Changed Start TCP/IP Listeners for the Test System"; to "Start ICE-XS
Listeners.
04/20/05 DMG Added End of Section
04/21/05 DMG Added Log files necessary for troubleshooting
04/22/05 JMK Modified info for stopping BASE24-es processes
04/25/05 DMG/DKE Lit edit changes
04/27/05 JMK Corrected a few typo’s and added stop of JDH
05/12/05 DMG Changed Heading 2 case to title case
06/07/05 JMK Added notes about esclean and ctend steps
06/08/05 JMK Added Checking System Status
06/09/05 DMG/DKE Changed esprocs to esstatus and lit edits.
06/24/05 JMK Added more “esclean” info
07/14/05 JMK Added verbage about installation of 3rd Party Software.
08/08/05 DMG Updated the Properties of this document
08/29/05 JMK Start of v05.4
Added info about evtlog messages, and c-tree user-id/password
9/22/05 JMK Updated ESWeb information
10/18/05 DMG Added the Desktop section
10/19/05 DMG Added the WebSphere directory as the location for starting ESWeb.
10/21/05 DMG 1. Removed the hard coded date in the following document:
Installing Electronically Distributed ACI Publications <ddMmmyyyy>.pdf
2. Moved Appendix A to after Appendix B
11/17/05 DMG 1. Changed manuals.zip to manuals1.zip
2. Added location of esinfo script.
01/03/06 JMK Added steps to start/stop the JMX process and location of the stopacijmx.
02/06/06 JMK Clarification of some steps.