Académique Documents
Professionnel Documents
Culture Documents
Connectivity
Installation Guide
This guide describes how to install Alliance Web Platform Server-Embedded on AIX.
27 March 2015
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Table of Contents
.Preface .............................................................................................................................................................................4
2 Introduction ....................................................................................................................................................... 6
2.1 Alliance Web Platform Server-Embedded ............................................................................................. 6
2.2 Roles in Alliance Web Platform and Management of Accounts ........................................................ 7
3 Preparation ........................................................................................................................................................ 9
3.1 Getting Started ........................................................................................................................................... 9
3.2 System Requirements .............................................................................................................................. 9
3.3 Hostname Resolution ............................................................................................................................. 10
3.4 Create the Alliance Web Platform Owner Account ............................................................................ 10
3.5 Modify Process Resource Allocation ................................................................................................... 11
3.6 Web Browser Settings ............................................................................................................................ 13
3.7 Prepare for Non-root Installation or Removal ..................................................................................... 15
3.8 Prepare the Response File for Silent Installation or Removal ......................................................... 16
3.9 Protect the Passwords in the Response File ...................................................................................... 17
3.10 Hosted Database ..................................................................................................................................... 18
3.11 Backup ...................................................................................................................................................... 19
4 Installation ........................................................................................................................................................ 21
4.1 Before You Begin .................................................................................................................................... 21
4.2 Interactive Installation ............................................................................................................................. 21
4.3 Silent Installation ..................................................................................................................................... 26
4.4 Next Steps ................................................................................................................................................ 26
5 Removal ............................................................................................................................................................ 28
5.1 Interactive Removal ................................................................................................................................ 28
5.2 Silent Removal ......................................................................................................................................... 28
5.3 Next Steps ................................................................................................................................................ 29
6 Patches .............................................................................................................................................................. 30
6.1 Install Patches ......................................................................................................................................... 30
6.2 Remove Patches ..................................................................................................................................... 31
7 Troubleshooting ............................................................................................................................................ 32
7.1 Support ..................................................................................................................................................... 32
7.2 Error Messages ....................................................................................................................................... 32
2 Installation Guide
Table of Contents
8.4 Upgrading the Operating System for Alliance Web Platform Server-Embedded
(Embedded Database) ........................................................................................................................... 41
8.5 Upgrading the Operating System for Alliance Web Platform Server-Embedded (Hosted
Database) ................................................................................................................................................. 42
.Legal Notices ...............................................................................................................................................................43
27 March 2015 3
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Preface
Purpose
This guide describes how to install, configure (more details in the Alliance Web Platform
Administration and Operations Guide), and uninstall Alliance Web Platform Server-Embedded.
Please check the Alliance Web Platform Server-Embedded Release Letter for any special or
last-minute installation information.
Audience
This guide is intended for those who are responsible for installing and configuring Alliance Web
Platform Server-Embedded.
Related documentation
The following guide is referenced:
4 Installation Guide
Installation Features Overview
Silent operations
You can perform the installation, patch, and removal operations silently. The main difference
between interactive (GUI-based) operations and operations performed silently is the way input
data is provided. In a GUI-based procedure, a user provides input through GUI windows. An
operation launched silently does not require interactive user input, instead a response file
provides this input.
The use of response files reduces the time required to perform and repeat the operation,
especially if you have a large number of instances. Furthermore, the use of a response file
allows for segregation of duties: operations managers can prepare the response files in
advance, and the operation itself can be scripted or carried out by other people of the
organisation. SWIFT provides templates of response files with default values, or alternatively,
you can run an interactive installation to generate a response file. For more information about
silent operations, see "Silent Operations" on page 34.
27 March 2015 5
Alliance Web Platform Server-Embedded 7.0.60 - AIX
2 Introduction
Alliance Web Platform Server-Embedded
Alliance Web Platform Server-Embedded is the framework that hosts browser-based graphical
user interfaces (GUI) of the Alliance portfolio. It offers a consistent end-user interface to the
functionality managed by Alliance Gateway or Alliance Access/Entry. Alliance Web Platform
Server-Embedded runs in an application server environment, enabling centralised deployment
of the software.
Alliance Web Platform Database TCP in the range 1541 and 1640
Alliance Web Platform Administration SwTL over SSL, or 48200 and 48201 for Alliance
Alliance Relationship Management SOAP over SSL Access/Entry
depending on the 48002/48003 for Alliance
Alliance Access/Entry Configuration packages. Gateway
Alliance Access/Entry Monitoring
Alliance Gateway Administration
Alliance Message Management
Browse
Alliance Integrator GUI
HTTPS secures the communication between the browser and the application server on which
Alliance Web Platform Server-Embedded and Alliance Web Platform Administration run. This
protocol requires a key/certificate to be deployed on the application server. A self-signed
certificate and its key are configured automatically during the Alliance Web Platform Server-
Embedded installation. In case of a patch upgrade, the certificate currently used is migrated.
6 Installation Guide
Introduction
Alliance Web Platform Server-Embedded hosts packages that communicate with an Alliance
server instance.
The communication between the application server and its database uses TCP and occurs on
the same host. The first free port in the range 1541 - 1640 is automatically configured during the
Alliance Web Platform Server-Embedded installation.
The Alliance Web Platform Server-Embedded installation also requires an additional port for
connectivity with the GlassFish Server Administration Console. The first free port in the range
23992-24090 is assigned. The default is 23992.
The application server provided with Alliance Web Platform Server-Embedded uses remote
method invocation to manage its internal processes. During the Alliance Web Platform Server-
Embedded installation, the first free port in the range 23991-24090 is assigned. The default is
23991.
Patch 7.0.60 requires an additional port, taken from the first free port in the range 23991-24090.
The default is 23993.
Note If the ports configured during the Alliance Web Platform Server-Embedded
installation are not suitable then you can use the swp_config tool to change the
values. The Alliance Web Platform Administration and Operations Guide explains
how to do this.
2.1.2 Requirements
Operating system and browser
Please refer to the Alliance Web Platform Server-Embedded Release Letter for detailed
information about the supported operating systems and browsers.
27 March 2015 7
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Note The sagsnlg group can contain several operating system accounts but each of
these accounts must be a SWIFT product owner account (for example, Alliance
Access, Alliance Gateway).
Note After patch 7.0.60 installation, the pre-existing Alliance Web Platform Users are
used. This operation is transparent to the end user.
8 Installation Guide
Preparation
3 Preparation
Target installation directory for upgrading 150% of current disk space usage with a
minimum of 7,500 MB
Additional space in target installation directory 500 MB per package deployed (including current
for GUI packages package deployments and planned future
package deployments)
If the disk space requirements for the temporary files for the program installation (see first
row in the table) cannot be satisfied, then the installer option -tempdir <TMPDIR> can be
used to specify an alternate temporary directory.
In this case, use the table above to determine disk space requirements.
2. Make sure that your hardware and installed software meet all installation requirements. Run
the checkhost tool against the Alliance Web Platform requirements file named
systemtest.dat. For more information, see "The Comparative Analysis Report" on page
41.
Note For the deployment of Alliance Web Platform, the minimum communication line
requirement between the platform server and the browsers is 64 Kbps.
System requirements
27 March 2015 9
Alliance Web Platform Server-Embedded 7.0.60 - AIX
You have to make sure that your /etc/netsvc.conf file contains the following line:
hosts=local4,bind4
This line ensures that the resolver checks the /etc/hosts file before DNS and ensures that
only IPv4 lookups are used.
Procedure
Verify that the /etc/hosts file contains a valid ip address in combination with the server name.
If /etc/hosts only contains a reference to localhost, you must add a line containing the IP
address and the server name.
A correct /etc/hosts file looks like the following example:
127.0.0.1 localhost
10.1.2.3 awp-se.example.com awp-se
2. Add a new user to the password file using your favourite system management tool. This
user is referred to as the Alliance Web Platform owner in the rest of the document.
The Alliance Web Platform owner account must be configured with the Korn shell as the
default login shell.
Note The sagsnlg group is created if it does not exist during the installation process and
the Alliance Web Platform owner account is added to this group. Alliance Gateway
and Alliance Access use the same group.
The steps in the following procedure are optional. If you want control over the
group ID of the sagsnlg group, then you must add a group called sagsnlg to the
group file with the ID of your choice before installing Alliance Web Platform. You
cannot change the group ID after installing Alliance Web Platform.
Important Do not use root as the Alliance Web Platform owner account.
10 Installation Guide
Preparation
2. Select one free group ID depending on your company policy. The group ID is the value in
the third column.
3. Create the group sagsnlg with the selected group ID by executing the commands:
mkgroup -A id=<group_ID> sagsnlg
2. Edit the ulimit settings as listed in the table above in the /etc/security/limits file.
4. Log off and log on again to ensure that the new settings are taken into account.
27 March 2015 11
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Procedure
To ensure the system will not choose a port that is already in use, It is recommended to set the
lower limit for ephemeral ports to a minimal value of 49152:
1. Login as root
Note High numbered ports should be used as ephemeral ports because they are less
likely to be used as port numbers for system services.
12 Installation Guide
Preparation
Procedure
1. Select the Internet Options from the Internet Explorer Tools menu.
5. Click OK .
Item Setting
HTTP 1.1 settings > Use HTTP 1.1 through proxy connections Must be selected
8. Click Apply .
27 March 2015 13
Alliance Web Platform Server-Embedded 7.0.60 - AIX
12. Add the Alliance Web Platform host to the Trusted sites zone.
Note It is important that the browser accepts the cookies sent by Alliance Web
Platform. Adding the Alliance Web Platform host in the list of trusted sites
normally takes care of this. However, local settings can possibly overrule this.
For example, In the Privacy tab, under Advanced , Override automatic cookie
handling allows you to override the cookie handling. If local settings are used,
then make sure that this custom configuration automatically accepts cookies
sent by Alliance Web Platform.
Item Setting
ActiveX controls and plug-ins > Run Active Controls and plug-ins Must be enabled
ActiveX controls and plug-ins > Script ActiveX controls marked safe Must be enabled
for scripting
Downloads > Automatic prompting for file downloads Must be enabled (only
valid for Internet
Explorer 8)
16. Click Settings in the Pop-up Blocker section. This button is available only if the Turn on
Pop-up Blocker check box is selected.
17. In the Address of website to allow field, enter the URL of the host where you will install
the Alliance Web Platform Server-Embedded software. Click Add .
3.6.2 Firefox
Prerequisites
Firefox ESR 24 is the qualified browser. The settings described below are required for all the
clients that connect to the Alliance Web Platform Server-Embedded (not on the server on which
Alliance Web Platform Server-Embedded is installed).
14 Installation Guide
Preparation
4. Click Exceptions... .
5. In the Address of website field, enter the hostname of the Alliance Web Platform Server-
Embedded.
6. Click Allow .
7. Click Close .
5. Restart Firefox.
5. Restart Firefox.
Preparation tasks
1. Log on with the root user account.
2. Add the non-root user account to the sagsnlg group, if not already done.
This non-root user will become the owner of the Alliance Web Platform Server-Embedded
installation.
27 March 2015 15
Alliance Web Platform Server-Embedded 7.0.60 - AIX
3. Verify that the /var/opt/swift directory exists. If it does not exist, then create it and set
permissions with the following commands:
mkdir -p /var/opt/swift
chmod 1777 /var/opt/swift
4. Create the installation directory with the correct ownership (<Alliance Web Platform
owner>:sagsnlg) and protections (750). The default directory path is:
/Alliance/WebPlatformSE
Important The user account that will run the installation must have full access to this
directory.
5. a. Create a directory named root under the installation directory with sufficient
permissions (700).
The installation directory was created in step 4 or, for an upgrade, the directory created
during the previous installation.
The Alliance Web Platform Server-Embedded owner account must own the root
directory.
c. Copy the oradism executable from the Alliance Web Platform Server-Embedded
release media to the root directory that you created. The oradism executable is
located in the same directory as the software installer.
Oracle uses the oradism tool to lock and unlock shared memory.
No "mount option" is allowed, in particular nosuid, on the file system where you install
Alliance Web Platform Server-Embedded. If your institution uses an NFS mount, then
consult IBM Support for information about the option for NFS mount.
where <install_dir> must be replaced with the path to the installation directory.
Important The user account that will run the installation must have read access to
this directory.
where <install_dir> must be replaced with the path to the installation directory.
16 Installation Guide
Preparation
You can prepare the response file in any of the following ways:
Record the input provided to a GUI-based procedure, using the -record option. For more
information, see "Record input parameters" on page 35.
Modify the sample response file provided on the Alliance Web Platform Server-Embedded
release media, as described in this section.
2. On the release media, in the folder for Alliance Web Platform Server-Embedded, navigate
to the installer directory.
3. Copy the appropriate response file from the Alliance Web Platform Server-Embedded
release media to a directory of your choice:
silent.properties.install.embedded
silent.properties.install.hosted
silent.properties.upgrade
silent.properties.uninstall
4. Edit the file to incorporate the required information. The file contains information about
which parameters are required.
For more information, see "Response File Parameters" on page 36.
5. Obfuscate or encrypt passwords or any other data by using the obfuscator tool provided on
the Alliance Web Platform Server-Embedded release media.
For more information, see "Protect the Passwords in the Response File" on page 17.
27 March 2015 17
Alliance Web Platform Server-Embedded 7.0.60 - AIX
2. Run the obfuscator tool, which creates a digest that hides the password.
To encrypt a password with a key that you provide, run the obfuscator tool with the -key
option.
If you use the -key option, you will be prompted to enter the key to be used. The same key
must be provided later to run the installation routine.
The key to be used must meet certain criteria:
The key must contain at least one uppercase character, one lowercase character, and
one numeral.
The number of occurrences of the same character must not exceed half the length of the
key.
4. Copy the resultant data displayed to the appropriate parameter in your response file.
2. An AL32UTF8 character set is required when you want to use an external, customer
provided Oracle instance.
3. In the database, database users and tablespaces must be configured and available.
The following tablespaces and associated datafiles are required:
Data Tablespace: The Tablespace from the hosted database where tables that hold the
Alliance Web Platform configuration data will be created. The minimum size for tablespace
is 250 MB. It is also recommended to switch the autoextend feature on.
Log Tablespace: The tablespace from the hosted database where tables that hold the
Alliance Web Platform event log data will be created. The minimum size for tablespace is
2500 MB. It is also recommended to switch the autoextend feature off.
18 Installation Guide
Preparation
4. The Alliance Web Platform schema owner account owns all the objects and data used by
the application. During installation, this account must be unlocked by the database
administrator and requires the following privileges:
CREATE SESSION
CREATE TABLE
CREATE SEQUENCE
CREATE VIEW
CREATE TRIGGER
CREATE PROCEDURE
CREATE JOB
UNLIMITED TABLESPACE
EXECUTE ON SYS.DBMS_LOCK
EXECUTE ON SYS.DBMS_LOB
SWIFT recommends that you lock and expire this account after the installation.
5. The user account is used by Alliance Web Platform Server-Embedded to access data. It
requires the following privileges:
CREATE SESSION
CREATE SYNONYM
After the installation the CREATE SYNONYM right can be removed.
3.11 Backup
Overview
It is strongly recommended to perform a DB backup as well as a backup of the SSL Certificate
before running the installation executable. In order to perform the backup, a standalone tool is
available. The tool extracts the pair of keys for the certificate configured in Alliance Web
Platform Server-Embedded and imports them into a specified keystore of your choice.
Procedure
1. Login as the Alliance Web Platform owner account
2. Copy all the files present in the exportkeystore directory of the installation media to the bin
directory of your Alliance Web Platform installation:
<SWP_INSTALL_PATH>/bin
3. Ensure those files are readable and executable for SWP owner.
27 March 2015 19
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Note To run swp_exportkeystore, the Alliance Web Platform owner must be logged
in.
20 Installation Guide
Installation
4 Installation
Overview
This procedure describes how to install the Alliance Web Platform Server-Embedded software.
You can install Alliance Web Platform Server-Embedded 7.0.60 on top of 7.0, 7.0.10, 7.0.20,
7.0.40, 7.0.50 or as a base installation. If you have Alliance Web Platform Server-Embedded
7.0.x already installed and that you want to perform a base installation, then you must first
uninstall the old release. For information about uninstalling Alliance Web Platform, see
"Removal" on page 28.
Note You can install (silent installation or interactive installation) Alliance Web Platform
Server-Embedded without root privileges. You must perform pre-configuration
tasks and then run the executable.
1. Verify your system requirements. For information about system requirements, see "System
Requirements" on page 9.
2. Create the Alliance Web Platform owner account. For information about creating the owner
account, see "Create the Alliance Web Platform Owner Account" on page 10.
3. For a silent installation, ensure that you have prepared the response file.
4. If you plan to install the software using a non-root user, then see the preparation
instructions in the section,"Prepare for Non-root Installation or Removal" on page 15.
5. Verify that the system resources are correctly set-up. For more information, see "Modify
Process Resource Allocation" on page 11.
6. Verify the web browser settings. For information, see "Web Browser Settings" on page 13.
7. Before installing patch 7.0.60 on top of the Alliance Web Platform Server-Embedded
7.0.40/7.0.50, you must ensure that at least one Alliance Web Platform user exists.
27 March 2015 21
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Note You can also launch the installer with a non-root account if you have
completed the non-root installation prerequisites.
4. If you are working remotely, then export the display to your local machine. Type the
following:
export DISPLAY=<IPaddressComputer>:0.0
where <IPaddressComputer> is replaced with the IP address for the computer that will
display the installation windows.
Note The installer has to be run from the installation release media.
Note If the command reports insufficient temporary disk space, then you can start
the installation using an alternative temporary directory. Enter:
./swp-se-install -tempdir /lfs/tmp
Continue with "Alliance Web Platform Server-Embedded Installation Steps" on page 22.
2. Click Next .
The End-user Licence window opens.
3. If you accept the terms, then select I have read and agree with the installation notice
and accompanying software licence terms (if any) above and click Next .
The Installation Location window opens.
22 Installation Guide
Installation
The Directory Name field contains a default path in which to install Alliance Web Platform
Server-Embedded.
/Alliance/WebPlatformSE
Important For the rest of this installation guide, the installation path is referred to as
<SWP_INSTALL_PATH>.
5. Verify that the correct information appears in the Owner field. This field displays the domain
name and user name of the Alliance Web Platform owner (or only the user name). This is
the user who will become the owner of the installation files upon completion of the
installation. Access to the installed files is restricted to this account.
This field will be read only when performing a non root installation.
Check the section "Roles in Alliance Web Platform and Management of Accounts" on page
7 for more details.
Host - host name where the Oracle Listener runs (allowed characters are a-z, 0-9, -). If
DNS is not used, then the hostname must be the IP address.
Port - port number of the Oracle Listener used to connect to the database instance. The
default value is 1521.
installation_checkhostreport_yymmdd_hhmmss.txt
installation_systemcheck_yymmdd_hhmmss.html
where yymmdd represents the installation date, and hhmmss represents the time of
installation.
If your system meets all the checked requirements, then continue with installation.
If your system does not meet the checked requirements, then the System Configuration
Test Results window opens.
The System Configuration Test Results window displays information about the problems
that were detected. Detailed information about any problem appears in the lower part of the
window.
27 March 2015 23
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Problems reported as Warning will not prevent you from continuing the installation, but
you may encounter unexpected results. Click Next .
Problems reported as Blocking will prevent you from continuing the installation. Cancel
the installation, fix the problem, and retry the installation.
9. Specify the name of the instance in the Instance Name field. Either accept the default
name SWP01 or enter an instance name.
The instance name must meet the following conditions:
It is unique amongst all Alliance Web Platform instances. The instance name provided is
used for configuration purposes. It cannot be changed after the Alliance Web Platform
Server-Embedded installation has finished.
11. If you have selected Hosted database, then the Database Passwords window opens. Fill
in the following fields to register the password for the Alliance Web Platform database
account.
Schema Owner
Password
Username
Password
The Schema Owner in Oracle is defined as the Oracle account that owns the tables
containing the configuration data.
Username is the Oracle account through which the application connects to the database to
retrieve the data.
Click Next to continue.
Enter an account name in the Administrator Name field for the Alliance Web Platform
administrator account. The default account name is swpadmin. The composition of any
24 Installation Guide
Installation
user name must be a string of minimum 8 and maximum 20 characters in length. The set
of allowed characters is A - Z, a _ z, 0 - 9.
Enter a password in the Administrator Password field for the Alliance Web Platform
administrator account.
Enter the same password again in the Administrator Password Confirmation field.
Note The Alliance Web Platform administrator account name and password are
required to log on to the Alliance Web Platform Administration application.
Verify that the full host name is displayed in the Host Name field. If the host name
includes a domain, then verify that it is correct (host.domain.com).
Note The host name and the port number define the URLs that are used to
access Alliance Web Platform and Alliance Web Platform Administration.
During the installation, a key and self-signed certificate are generated to
secure the communication between the browser and the application server.
The full host name will be used to build the DN (cn=<hostname>) of that
certificate.
Note Once you click Install , it is not possible to abort the software installation.
18. The installer copies files and configures Alliance Web Platform Server-Embedded which
may take a few minutes. When the installation is complete, the Installation Complete
window opens.
19. Click Finish to apply installation settings and complete the installation.
27 March 2015 25
Alliance Web Platform Server-Embedded 7.0.60 - AIX
If there are any errors during this installation, then check the installation.log file in the target
installation location for correctness of the parameters.
2. Open a command prompt with the Alliance Web Platform owner account.
3. Navigate to the bin directory, one level below the directory where you have installed
Alliance Web Platform Server-Embedded.
Suggested path during installation:
<SWP_INSTALL_PATH>/bin
26 Installation Guide
Installation
27 March 2015 27
Alliance Web Platform Server-Embedded 7.0.60 - AIX
5 Removal
Overview
If it is necessary to remove the Alliance Web Platform Server-Embedded (for example, if an
error occurred during installation), then you can achieve a clean uninstall using the procedures
in this section.
Important If you do not use the uninstall procedures described in this section, then you may
have difficulties to reinstall Alliance Web Platform Server-Embedded. Always use
the uninstall application.
3. If you are working remotely, then export the display to your local machine. Type the
following: export DISPLAY=<IPaddressComputer>:0.0
where <IPaddressComputer> is replaced with the IP address for the computer that will
display the installation windows.
Follow the instructions on screen to complete the uninstallation of Alliance Web Platform
Server-Embedded.
28 Installation Guide
Removal
4. If the database is hosted, then you must do a clean-up of the database. The clean-up will
undo everything that has been installed in the hosted database, including the two database
accounts.
27 March 2015 29
Alliance Web Platform Server-Embedded 7.0.60 - AIX
6 Patches
Cumulative patches, which are sent to all Alliance Web Platform customers. Each cumulative
patch includes the previous cumulative patch and any optional patches issued after the
previous cumulative patch.
Optional (emergency) patches, which are sent to selected Alliance Web Platform customers
and which affect specific deliverables, such as executables and library files. Optional patches
do not include any previous patches.
A new version (release or patch) of a package is deployed on top of Alliance Web Platform
Server-Embedded by installing the new package next to the existing deployed package. The old
version of a package is not removed when you install a new version. You must uninstall
packages manually. When installing a new version of a package (for which an older version is
already deployed in Alliance Web Platform), the configuration of the old package is copied to
the new package.
Prerequisites
Before installing a patch, you must:
3. Read the patch release letter carefully. It describes the scope of the patch and the
installation instructions.
For cumulative patches:
Installing a patch replaces the product deliverables of this patch with new, patched versions.
The previous versions of the deliverables are stored by the patch installation software and
can be restored when the patch is removed.
30 Installation Guide
Patches
Prerequisites
27 March 2015 31
Alliance Web Platform Server-Embedded 7.0.60 - AIX
7 Troubleshooting
7.1 Support
Support for SWIFT customers
By default, SWIFT is the single point of contact to report all problems and queries that relate to
SWIFT services and products. Support is available to all SWIFT customers.
Individuals within a customer organisation must register to use the Support service.
The different services that SWIFT offers as part of the support packages and the procedure to
order support are described at www.swift.com > Support > Support services > Support offer
overview.
Related information
For more information about Support services, see the service description related to the
applicable support package.
Check the installation log file, systemcheck, and checkhost report files which are created
during installation. These files contain information about potential errors or warnings which
occurred during installation.
If you are using a hosted database, then check the prerequisites again.
Check the event log of Alliance Web Platform Server-Embedded with Alliance Web Platform
Administration or execute swp_readlog in the command prompt.
Support
The support.html page allows you to display some Internet Explorer settings that are important
to use Alliance Web Platform Server-Embedded. You can use this page to verify that your
current web browser settings follow the required settings.
To display the page, type the following https://<host>:<port>/swp/support.html
Where:
32 Installation Guide
Troubleshooting
The <port> is the port number of the application server on which Alliance Web Platform is
deployed. The default port number is 2443.
When the login page is displayed, Internet Explorer checks whether the cookies and JavaScript
are enabled. If they are not enabled, then a warning message is displayed.
27 March 2015 33
Alliance Web Platform Server-Embedded 7.0.60 - AIX
8 Additional Information
1. The root user logs on and prepares for the non-root installation. For more information, see
"Prepare for Non-root Installation or Removal" on page 15.
2. A non-root user logs on using the owner account and launches the installer to begin the
installation.
Checkhost
If a non-root user account runs the installation, then some of the checkhost checks may fail
because of the privileges associated with the account. Typically, these will be warnings. The
checkhost report will include information about any such failures.
Benefits
Silent operations have the following benefits:
They do not require firewall administrators to open many ports to support the X-Display
necessary for a GUI. This makes it easier and more secure to connect to remote servers or
servers behind a firewall.
They simplify the repetition of an operation over several instances of the same product, by
reusing the response files after editing them.
They allow for the segregation of duties: operations managers can prepare the response files
in advance, and the operation can be scripted or performed by other people of the
organisation.
The use of passwords in silent operations is as secure as in interactive operations. The system
account password is made unreadable in the response file. For more information, see "Protect
the Passwords in the Response File" on page 17.
34 Installation Guide
Additional Information
Scope
The following Alliance Web Platform Server-Embedded operations can be performed silently:
Installation
Removal
Patch installation
Patch removal
Purpose
A response file provides the input that is required to complete a silent procedure.
If you plan to perform a procedure silently, then you must first prepare a response file.
Record the input during an interactive procedure, using the -record option. See "Record
input parameters" on page 35.
Modify the sample response file that is provided on the release media. See "Prepare the
Response File for Silent Installation or Removal" on page 16.
Modify an existing response file, which you created previously during installation or removal.
The release media contains sample response files (with extension .properties).
Obfuscate or encrypt any password that is entered, before it is stored in the response file.
The syntax for the -record option is as in the following example:
swp-se-install -record <response file> [-key <value>]
Where:
<response file> identifies the path to and name of the file to be used to record the
parameters.
-key <value>, if used, indicates that the passwords in the response file are encrypted with
the provided encryption key. If this parameter is omitted, then the passwords are obfuscated.
27 March 2015 35
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Purpose
This section describes the possible parameters and indicates their applicability in installation-
related operations.
O = optional parameter on all platforms. If the parameter is not specified, then the default
value is used.
- = not relevant.
Installation
Removal
Upgrade
Parameter Description
36 Installation Guide
Additional Information
Installation
Removal
Upgrade
Parameter Description
27 March 2015 37
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Installation
Removal
Upgrade
Parameter Description
Embedded. If not specified,
then the administrator
account name is set to:
swpadmin.
A comparative analysis report: this report compares a host machine against a list of minimum
requirements provided in a requirements file.
The checkhost tool is integrated in the Alliance Web Platform Server-Embedded installer as
well and provides an on-screen report of possible discrepancies during the Alliance Web
Platform Server-Embedded installation. See "checkhost Syntax and Examples" on page 39 for
detailed information about the uses of the checkhost tool.
38 Installation Guide
Additional Information
4. Launch the checkhost tool. See "checkhost Syntax and Examples" on page 39 for
syntax information.
where:
Text wrapped in square brackets [....] represents an optional part of the command.
Text wrapped in angle brackets <....> represents values that you must supply.
Options
-req
Use this option to specify the path to a requirements file.
-rootdir
Use this option to specify the path to a drive or file system against which the checkhost tool
must perform a disk space validation.
-out
Use this option to specify a location for the report file. If not used, then the report is produced in
the following default location:
-outxml
Use this option to specify a location for the file containing the report in XML format.
-stdout
Use this option to route the report to stdout.
27 March 2015 39
Alliance Web Platform Server-Embedded 7.0.60 - AIX
OS version Yes
IP addresses Yes
OS language No
(1) CPU speed: The checkhost tool prints the value as reported by the operating system.
(2) Memory size: The checkhost tool prints the value as reported by the operating system.
(3) Network adapters: Details about all the available network interfaces (except the loopback adapter) such as
domain name, MAC address, and the kernel routing tables that configure these network adapters are reported.
(4) Network options: Details about the configuration of the network driver, such as, tcp close wait interval, arp
cleanup interval, and so on, are reported. The exact output is different on every platform because the level of detail
and the different options are heavily dependent on the architecture.
40 Installation Guide
Additional Information
Requirements file
The following requirements file is found on the Alliance Web Platform Server-Embedded media.
systemtest.dat Contains the base requirements for Alliance Web Platform Server-Embedded
installation.
Procedure
1. Use swp_config -packages -list to check the Alliance Web Platform patch level.
5. Install Alliance Web Platform 7.0 (or any other base release such as 7.0.50 or 7.0.60).
27 March 2015 41
Alliance Web Platform Server-Embedded 7.0.60 - AIX
Procedure
1. Use swp_config -packages -list to check the Alliance Web Platform patch level.
5. Install Alliance Web Platform 7.0 (or any other base release such as 7.0.50 or 7.0.60). Use
the "dummy" database schema during installation.
9. Use swp_config -hosteddb to change the database parameters to point to the original
schema.
11. Use swp_config -syncdb to synchronize the database to load the installed packages in
the application server.
42 Installation Guide
Legal Notices
Legal Notices
Copyright
SWIFT 2015. All rights reserved.
Restricted Distribution
Do not distribute this publication outside your organisation unless your subscription or order expressly grants
you that right, in which case ensure you comply with any other applicable conditions.
Disclaimer
The information in this publication may change from time to time. You must always refer to the latest
available version.
Translations
The English version of SWIFT documentation is the only official and binding version.
Trademarks
SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT: the SWIFT
logo, SWIFT, SWIFTNet, Accord, Sibos, 3SKey, Innotribe, the Standards Forum logo, MyStandards, and
SWIFT Institute. Other product, service, or company names in this publication are trade names, trademarks,
or registered trademarks of their respective owners.
27 March 2015 43