Ensure that the hardware meets the minimum requirements. For more information on minimum server machine hardware requirements, see Avaya Experience Portal Overview and Specification on http://support.avaya.com.

For minimum hardware requirements, see Minimum (Linux) server machine hardware requirements.

What access method are you going to use?

______ Local keyboard, mouse, and monitor

______ Remote access via SSH client

Server information

IP address

______________________

Host name

______________________

The host name cannot contain spaces or periods.

Avaya Enterprise Linux network configuration information

Subnet mask on Corporate LAN

______________________

Default gateway

______________________

Primary DNS Server

______________________

DNS domain name

______________________

Time zone

______________________

For more information about the Avaya-provided server installation, see Implementing Avaya Experience Portal on multiple servers.

For customer-provided hardware, is Release 7.x or 8.x 64 bit or newer update installed?

______ Yes

______ No

If No, install Release 7.x or 8.x 64 bit or later as described in Implementing Avaya Experience Portal on multiple servers.

Is the default language for Linux set to English?

______ Yes

______ No

If No, set the default language to English. You can change the default language after Experience Portal is installed.

Can all planned Experience Portal servers communicate with one another?

______ Yes

______ No

For more information about verifying server communication, see Implementing Avaya Experience Portal on multiple servers on http://support.avaya.com.

For Avaya Enterprise Linux, user account passwords

cust account password: ___________________

root account password: ___________________

For Red Hat Enterprise Linux Server, user accounts and passwords

root account password: ___________________

Non-root account name: ____________________

Non-root account password: _________________

Can you log in to the Experience Portal server with the non-root account name and password?

______ Yes

______ No

The upgrade tool deletes all existing root accounts. Therefore, after the upgrade, the administrator can use the non-root account name and password to log in and:

• Install a new Authentication File System (AFS) file.

• Activate the Avaya service accounts.

Installation directory, if different from default

______________________

Default directory: /opt/Avaya/ExperiencePortal

Specify an absolute directory path containing only standard English alphanumeric characters and the symbols / (forward slash), _ (underscore), - (hyphen), ~ (tilde), or . (period).

Auxiliary EPM database password

______________________

For more information about the Primary EPM server installation worksheet, see Implementing Avaya Experience Portal on multiple servers.

Do you want to create a database account that can access the report information in the database?

______ Yes

______ No

If Yes, account user name, if different from the default: ______________

Password: __________________________

Default user name is: reportwriter

Do you want to create a report writer database account that allows external Experience Portal servers to write report data into the Experience Portal database on this server.

______ Yes

______ No

If Yes, account username: ______________________

If Yes, account password: ___________________

Third-party SSL certificate information.

Third-party SSL certificate information.

The location of the existing certificate:

______________________

The existing certificate’s password: _________________

Will Avaya Services maintain this server?

______ Yes

______ No

If Yes, what is the Listed Directory Number (LDN) for this server?

______________________

Where is the Avaya Service Account authentication file located?

______________________