AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
No results found
Search suggestions:
- Use fewer tags and filters.
- Use different search terms.
Filters
AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
No results found
Search suggestions:
- Use fewer tags and filters.
- Use different search terms.
Filters
Avaya Experience Portal Documentation Library
Table of Contents
Type to filter navigation items by title
AEP installation script
Last Updated : Feb 14, 2022 |
Prolog information
Metadata
Keywords:
The AEP installation script for all server types uses the aepinstall.sh script. This script is included in the AEP ISO that is being installed. For example, AEP-8.x.iso. The script does the following:
-
Checks the server using the pre-requisite or Platform Vendor Independent (PVI) checker to verify that minimum hardware requirements and OS RPM packages are installed, and other OS configurations are completed.
-
Installs Primary EPM, Auxiliary EPM, Standalone MPP, or the co-resident Primary EPM or MPP.
-
Supports headless installs of the servers using an XML file in all required settings.
AEP installation script parameters
The AEP installation script has the following parameters:
|
-help
|
Prints out help.
|
|
-pvicheck
|
Runs the pre-requisite (PVI) checker and generates a report in /opt/Avaya/InstallLogs/pvicheck.log.
|
|
-headless input-file.xml
|
Allows headless (silent) install of any AEP server type.
|
|
-autoupgrade
|
Not correctly supported.
|
AEP headless (silent) installation
The AEP installer supports the ability to be headless, which means installation of any server type without user interaction. This is accomplished with the use of an xml file that is passed into the installer.
The AEP ISO that is being installed has a template version of an xml file that can be used as an example. The file is called aepinstallconfig.xmland has the following elements:
<Global> element:
The Global element must be included for all server types. It contains the following element:
|
<InstallType>
|
Must have one of the following values:
|
<PrimaryEPM> element
The <PrimaryEPM> element must exist if the server type is Primary EPM or Single Server - Primary EPM and MPP. It contains the following elements:
|
<WebAdminUsername>
|
Username for AEP web admin login
|
|
<WebAdminPassword>
|
Password for AEP web admin login
|
|
<CreateDBAccountForAux>
|
Boolean for vpcommon account creation for the auxiliary server connection
|
|
<DBAccountForAuxPassword>
|
vpcommon password
|
|
<EnableEASG>
|
Disable or enable EASG
|
|
<ProductIdentifier>
|
10 digit Product ID
|
<AuxiliaryEPM> element
The <AuxiliaryEPM> element must exist if the server type is Auxiliary EPM. It contains the following elements:
|
<PrimaryEPMHostnameOrIPAddress>
|
Primary EPM IP address or hostname
|
|
<PrimaryEPMDBPassword>
|
Primary EPM vpcommon password
|
|
<CreateReportWriterUser>
|
Boolean for DB Report writer account creation
|
|
<ReportWriterUsername>
|
Report writer username
|
|
<ReportWriterPassword>
|
Report writer password
|
<CommonEPM> element
The <CommonEPM> element must exist if the server type is Primary EPM, Single Server - Primary EPM and MPP, or Auxiliary EPM. It contains the following elements:
|
<CreateReportReaderUser>
|
Boolean for DB Report reader account creation
|
|
<ReportReaderUsername>
|
Report reader username
|
|
<ReportReaderPassword>
|
Report reader password
|
<MPP> element
The <MPP> element must exist if the server type is Standalone MPP or Single Server - Primary EPM and MPP. It contains the following element:
|
<MPPEPMHostnameOrIPAddress>
|
Primary EPM IP address or hostname
|