Awp Serv Embedded 7 0 60 Inst Guid Aix PDF

AIX
Connectivity
Alliance Web Platform Server-Embedded 7.0.60
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
1 Installation Features Overview ................................................................................................................. 5
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
8 Additional Information ................................................................................................................................ 34

8.1 Non-root Installation ................................................................................................................................ 34
8.2 Silent Operations ..................................................................................................................................... 34
8.3 Check Your System Configuration ....................................................................................................... 38
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
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:
Alliance Web Platform Administration and Operations Guide
Installation Features Overview
1 Installation Features Overview

Introduction
This section describes the installation-related features that are available for Alliance Web
Hosted database or embedded database

In an embedded database environment, the product software uses the database supplied with
the product. In a hosted database environment, you install Alliance Web Platform Server-
Embedded within an existing database.
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.
Recording the installation

The interactive installation features the option to record the input information provided during
the installation into a response file. A command-line based silent installation procedure can use
this response file to provide the same installation information in subsequent installations. This
reduces the risk of human error from manual intervention.
For more information about recording the installation, see "Response Files Configuration" on
page 35.
Performing actions as a non-root user

It is possible to install, patch, or remove the Alliance Web Platform Server-Embedded software
with a non-root user account. The non-root user account that installs Alliance Web Platform
Server-Embedded becomes the owner of the instance.
Before you can take an action (such as installation) with a non-root user account, the root user
must prepare the system for the action that the non-root user will perform.
For more information, see "Non-root Installation" on page 34.
27 March 2015 5
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.
What SWIFT delivers

SWIFT delivers the Alliance Web Platform Server-Embedded application (including the Alliance
Web Platform Administration GUI), an application server, and a database for embedded use.
2.1 Alliance Web Platform Server-Embedded

Definition
The installer for Alliance Web Platform Server-Embedded installs and configures the application
server that Alliance Web Platform Server-Embedded requires, customising it based on values
provided during installation. When the installation finishes, the application server is already
running and the Alliance Web Platform Server-Embedded software is ready to use.
The application server for Alliance Web Platform Server-Embedded remains transparent after
installation. It starts and stops along with the operating system.
2.1.1 Communication Protocols and Ports

Overview
The following table describes the various communication links, protocols, and ports used:
Communication link Protocol Default port
Browser - Alliance Web Platform/Administration HTTPS 2443
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
Note Alliance Message Management uses SwTL and SOAP.
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.
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.
2.2 Roles in Alliance Web Platform and Management

of Accounts
Introduction
This section describes the various roles involved in the Alliance Web Platform Server-
Embedded installation.
2.2.1 Alliance Web Platform Owner

Concept
The Alliance Web Platform owner owns the Alliance Web Platform Server-Embedded
installation (files). An operating system account identifies the Alliance Web Platform owner.
Access to all the files under the Alliance Web Platform Server-Embedded installation directory is
restricted to this operating system account.
When using the embedded database installation option, the Alliance Web Platform owner also
owns the Alliance Web Platform Server-Embedded database (has full access to the database).
At the end of the Alliance Web Platform Server-Embedded installation, the Alliance Web
Platform owner account belongs to the group sagsnlg.
27 March 2015 7
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).
2.2.2 Alliance Web Platform Users

Concept
Alliance Web Platform Users connect to the Alliance Web Platform Administration package
from the web browser. This package is used to configure and administer Alliance Web
Platform
Note After patch 7.0.60 installation, the pre-existing Alliance Web Platform Users are
used. This operation is transparent to the end user.
2.2.3 Alliance Server Users

Concept
Alliance Server Users connect to the relevant packages from the web browser. They are
defined by the relevant Alliance Server Instance.
Example: For Browse, users of the package are SWIFTNet users defined in the Alliance
Gateway instance. The Browse users are authenticated at login time against the Alliance
Gateway instance configured by the Alliance Web Platform administrator. Similarly, users of
Alliance Access/Entry packages must be defined as operators in the relevant Alliance Access/
Entry instance.
Preparation
3 Preparation
3.1 Getting Started

Installation media
The Release Letter lists the channels through which the Alliance Web Platform Server-
Embedded software is distributed. In this guide, "release media" refers to any media that
provides the software, for example, a DVD, or a file downloaded from www.swift.com.
Alliance Web Platform Server-Embedded embeds certain third-party software, in whole or in
part, which are described in the Alliance Web Platform Server-Embedded Installation Notice,
including the terms and conditions under which they are used. This Installation Notice is
contained within the software medium.
3.2 System Requirements

Requirements list
Ensure that your system complies with the requirements in the following list:
1. Verify the disk space requirements on the machine where you intend to install Alliance Web
Requirement Disk space requirement
Temporary files for program installation 1,200 MB in /var/tmp/

If /var/tmp is not writable, then /tmp is used.
Target installation directory for embedded 5,000 MB minimum; 10,000 MB recommended

database
Target installation directory for hosted database 1,024 MB
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
A Korn shell is required.
27 March 2015 9
Only a 64-bit kernel is supported.
The hardware processor must have 64 bits.
Alliance Web Platform Server-Embedded installers are graphical applications. A dedicated X

display terminal is required to run the installer.
Note A X display terminal is not needed if you run a silent installation.
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.
3.3 Hostname Resolution

Overview
/etc/hosts must contain two entries for the local hostname and loopback (ipv4)
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
3.4 Create the Alliance Web Platform Owner Account

Create the Alliance Web Platform owner account
1. Log on as root on the host machine where the Alliance Web Platform Server-Embedded
will be installed.
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.
Preparation
Create the sagsnlg group

Before installing Alliance Web Platform, create the sagsnlg group by completing the steps in
the following procedure:
1. Edit the /etc/group file to find a group ID that is not yet in use. Each line of the /etc/group
file looks like:
sagsnlg::<group_ID>:
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
3.5 Modify Process Resource Allocation

Overview
This procedure describes how to set and to verify the resource control values for the Ulimit
settings and the dev_attributes configuration.
3.5.1 Ulimit Settings

Introduction
The following table summarises the ulimit settings required for Alliance Web Platform Server-
Embedded.
Setting Parameter name Value
Coredump core Unlimited
Data data Unlimited
File fsize Unlimited
Memory rss_hard Unlimited

rss
Nofiles nofile 4096
Processes nproc Unlimited
Stack stack Unlimited
Time cpu Unlimited
Edit ulimit settings

1. Log on as root.
2. Edit the ulimit settings as listed in the table above in the /etc/security/limits file.
3. Save the file.
4. Log off and log on again to ensure that the new settings are taken into account.
27 March 2015 11
Verify the ulimit settings

1. Log on with the Alliance Web Platform owner account.
2. Run the following command:

$ulimit -a
The output must be similar to the following:

time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) 4096
processes(per user) unlimited
3.5.2 Ephemeral Ports Settings

Overview
Ephemeral ports are temporary ports assigned by a machine's IP stack, and are assigned from
a designated range of ports for this purpose.
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
2. Update the script /etc/rc.tcpip with the following lines:

/usr/sbin/no -o tcp_ephemeral_low=49152
/usr/sbin/no -o udp_ephemeral_low=49152
Those lines must be added before the script starts the server daemons.
Note High numbered ports should be used as ephemeral ports because they are less
likely to be used as port numbers for system services.
3.5.3 dev_attributes Configuration

To set the kernel parameters
1. Log on as root.
2. Turn off AIX 4.3 core generation.

#chdev -l sys0 -a pre430core='false'
3. Change the ncargs value.

#chdev -l sys0 -a ncargs=256
4. Change the maxuproc value.

#chdev -l sys0 -a maxuproc=16384
5. Reboot your system.
Preparation
To verify the kernel parameters

1. Log on as root.
2. Run the following commands to verify the kernel parameters.

# lsattr -E -l sys0 -a maxuproc -F value
16384
# lsattr -E -l sys0 -a ncargs -F value
256
3.6 Web Browser Settings

3.6.1 Internet Explorer
Prerequisites
Internet Explorer 8, 9, 10 and 11 are the qualified browsers. The settings listed in the table 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). Make sure that the
following settings are selected or enabled.
Procedure
1. Select the Internet Options from the Internet Explorer Tools menu.
2. Select the General tab.
3. Click Settings in the Browsing history section.
4. Set the Check for newer versions of stored pages to Automatically.
5. Click OK .
6. Select the Advanced tab.
7. Verify the following settings:
Item Setting
HTTP 1.1 settings > Use HTTP 1.1 Must be selected
HTTP 1.1 settings > Use HTTP 1.1 through proxy connections Must be selected
Security > Use TLS 1.0 At least one TLS

Security > Use TLS 1.1 security level must be
selected, as per your
Security > Use TLS 1.2 internal security
recommendation.
Security > Use SSL 2.0 Must NOT be selected
Security > Use SSL 3.0 Must NOT be

selected(1)
Security > Warn about certificate address mismatch Must be selected
(1) See Knowledge base tip 5019465.
8. Click Apply .
9. Select the Security tab.
27 March 2015 13
10. Select the Trusted sites zone.
11. Click Sites .
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.
13. Click Custom level .

The Security Settings window opens.
14. Verify the following settings:
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)
Downloads > File download Must be enabled
Scripting > Active scripting Must be enabled
Scripting > Scripting of Java applets Must be enabled
15. Select the Privacy tab.
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 .
18. Click Close .
19. Click OK in the Internet Options window to save the changes.
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).
Preparation
Unlock pop-up windows

1. Open the Firefox options.
2. Click the Content panel.
3. Enable Block pop-up windows.
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 .
Disable SSL 3.0

1. Type about:config in the address bar.
2. Click I'll be careful, I promise!
3. Search for property security.tls.version.min.
4. Set the value to 1.
5. Restart Firefox.
Enable TLS 1.2 (Optional)

1. Type about:config in the address bar.
2. Click I'll be careful, I promise!
3. Search for property security.tls.version.max.
4. Set the value to 3.
5. Restart Firefox.
3.7 Prepare for Non-root Installation or Removal

Introduction
The user that installs the Alliance Web Platform Server-Embedded software becomes the owner
of the Alliance Web Platform Server-Embedded instance. To prepare for a backup, installation,
or removal operation of Alliance Web Platform Server-Embedded with an account that does not
have root privileges, the root account must perform specific tasks before the operation.
You can ignore this section if you intend to perform these actions with the root user account.
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
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.
b. Change the ownership of the root directory, as follows:

/usr/bin/chown <alliance web platform owner account>:sagsnlg
<install_dir>/root
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.
d. Change the ownership of oradism executable to root:sagsnlg. Type:

/usr/bin/chown root:sagsnlg <install_dir>/root/oradism
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.
e. Change the permissions of the oradism executable. Type:

/usr/bin/chmod 4755 <install_dir>/root/oradism
where <install_dir> must be replaced with the path to the installation directory.
3.8 Prepare the Response File for Silent Installation

or Removal
Purpose
A response file provides all the user input required to complete a procedure silently.
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.
Modify a previously created response file.
Modify the response file provided on the release media

1. Access the Alliance Web Platform Server-Embedded release media.
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.
6. Save the file.

If you intend to perform a non-root installation, then save the file so that it can be read by
the user account that performs the non-root installation.
3.9 Protect the Passwords in the Response File

Principle
Silent installation operations require that the system passwords are present in the response file.
In the response file, the passwords or any other data can be specified in clear text, obfuscated,
or encrypted (which is the recommended option for passwords).
A tool is provided on the Alliance Web Platform Server-Embedded release media to obfuscate
or encrypt passwords or any other data.
Run the obfuscator tool

1. On the Alliance Web Platform Server-Embedded release media, navigate to the installer
directory for your operating system.
27 March 2015 17
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 length of the key must be in the range of 8 - 20 characters.
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.
3. You are prompted to enter the data (password) to be obfuscated or encrypted.

The result is displayed.
4. Copy the resultant data displayed to the appropriate parameter in your response file.
3.10 Hosted Database

Introduction
Alliance Web Platform Server-Embedded supports the configuration of the Alliance Web
Platform database on an external, customer provided Oracle instance. This instance can be
located on the same host as Alliance Web Platform Server-Embedded or a different host. You
cannot manually start or stop the database when connecting to a hosted database. During an
upgrade of the Alliance Web Platform Server-Embedded, you cannot change the database to a
hosted database.
Prerequisites for new installations

The hosted database must be set up as follows before installing Alliance Web Platform Server-
Embedded:
1. An Oracle Standard Edition or Enterprise Edition database must be available. For the exact
version information, see the Alliance Web Platform 7.0.60 Release Letter.
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.
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.
4. Execute the command swp_exportkeystore.

The command swp_exportkeystore has the exact same syntax and behaviour than the
command swp_config -exportcert. See the section about the configuration tool in the
Alliance Web Platform Administration and Operations Guide for more information.
27 March 2015 19
The tool exports a certificate and its keys.
Note To run swp_exportkeystore, the Alliance Web Platform owner must be logged
in.
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.
4.1 Before You Begin

4.1.1 Checklist
Tasks
Complete these tasks before installing Alliance Web Platform Server-Embedded.
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.
4.2 Interactive Installation

4.2.1 Launch the Alliance Web Platform Server-Embedded
Software Installer
Procedure
1. Log on with the root account.
27 March 2015 21
Note You can also launch the installer with a non-root account if you have
completed the non-root installation prerequisites.
2. Open a Korn shell.
3. Access the release media.
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.
5. Navigate to the following directory on the installation release media:

AIX/installer
Note The installer has to be run from the installation release media.
6. At the prompt, enter:

./swp-se-install
To record the installation details for future use, run the ./swp-se-install command
with the -record option. For more information, see "Record input parameters" on page
35.
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
where /lfs/tmp points to a local directory on a device with at least 1,200 MB

free disk space.
The temporary directory must be outside the installation path.
For example, you cannot specify /Alliance/WebPlatformSE/tmp if the
installation directory is /Alliance/WebPlatformSE.
Continue with "Alliance Web Platform Server-Embedded Installation Steps" on page 22.
4.2.2 Alliance Web Platform Server-Embedded Installation

Steps
Procedure
1. When the installer files are unpacked, the Welcome to the Alliance Web Platform
Installer window opens for installation of Alliance Web Platform Server-Embedded.
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.
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>.
4. Specify the location where Alliance Web Platform Server-Embedded is to be installed.

Either accept the default path or click Browse to select another path.
Do not use spaces in the path name.
Do not specify a symbolic link. You must give the full physical path.
Use a directory that is dedicated to this product.
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.
6. Select either Embedded or Hosted in the Database field.

If you select Hosted in the Database field, then enter the following:
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.
Service - Oracle Service ID of the database instance.

Click Next to continue.
7. A system configuration test is performed on your system.

The results of this test are saved in the installation directory, in the files:
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
The Result column specifies the severity of a reported problem:
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.
8. The Instance Configuration window opens.
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.
It begins with an alphabetical character (A-Z).
It is between 3 and 8 alphanumeric characters (A-Z, 0-9).
The characters are all uppercase. No lowercase characters allowed.
10. Click Next .
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.
12. The Database Tablespaces Remapping window appears.

In the Data Tablespace field, enter the name of the tablespace that you have created to
hold the Alliance Web Platform configuration data.
In the Log Tablespace field, enter the name of the tablespace that you have created to
hold the Alliance Web Platform event log.
13. The Instance Configuration window appears.
14. Enter the required parameters to set up the application:
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
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.
Note The password must be a minimum of eight and a maximum of 30

characters in length. The password must contain at least three elements out
of the following sets:
A - Z (O upper case excluded)
a - z (o lower case excluded)
0 - 9 (number 0 excluded)
!?@#$%&+-*/=
If a patch of Alliance Web Platform Server-Embedded is installed,
passwords created with the previous versions of the Alliance Web
Platform Server-Embedded do not have to match the password
composition policy until they are reset or changed.
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).
Specify the HTTPS port number in the Port Number field.
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.
15. Click Next .
16. The Installation Summary window opens.
17. Click Install .
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
4.3 Silent Installation

Procedure
2. Navigate to the following directory:

AIX/installer
3. Type the following command:

swp-se-install -silent <path> -key <value>
where <path> defines the path of the response file location.

The response file includes the passwords. They can be specified in clear text, obfuscated
or encrypted. If the response file contains encrypted passwords, the key used for
encrypting must be provided while launching the installation. You can use the -key
<value> option to decrypt the passwords present in the response file. If you do not use the
-key <value> option, the installer automatically detects that a key is required to decrypt
the password and prompts for a value.
If there are any errors during this installation, then check the installation.log file in the target
installation location for correctness of the parameters.
4.4 Next Steps

4.4.1 Install Packages
Introduction
Alliance Web Platform Server-Embedded allows the installation of packages. The packages are
deployed on the Alliance Web Platform Server-Embedded. The applications included in the
packages can be configured and made available within an application group.
You can install multiple versions of the same package (from different release numbers).
Packages are delivered as EAR files.
Packages are delivered together with the Alliance server products that provide the services
accessible through the Alliance Web Platform Server-Embedded.
Install a package on the Alliance Web Platform Server-Embedded

1. Use the swp_config command to install the package on Alliance Web Platform Server-
Embedded.
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
4. Enter the swp_config command:

swp_config -packages -install -file <PACKAGE_FILE_PATH>
Installation
where <PACKAGE_FILE_PATH> is replaced with the path to the package file.

The swp_config command automatically installs the package in the embedded application
server of Alliance Web Platform Server-Embedded.
4.4.2 Configure Alliance Server Instances

Overview
Alliance server instances must be configured in Alliance Web Platform Server-Embedded.
Alliance server instances are configured to check the SSL certificate validity, distinguished
name, and valid port number. They are configured to know the status of the server instance (to
test the connectivity of the server instance). An Alliance server instance can be an Alliance
Access/Entry instance or an Alliance Gateway instance. For more information about creating
and deleting Alliance server instances, see the Alliance Web Platform Administration and
Operations Guide.
4.4.3 Update /etc/services

Overview
You must modify the /etc/services file to specify which ports will be used by the application
server for Alliance Web Platform.
27 March 2015 27
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.
5.1 Interactive Removal

Uninstall the Alliance Web Platform Server-Embedded software
1. Log on as root or as Alliance Web Platform owner on the host machine where Alliance
Web Platform is installed.
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.
4. Run the <SWP_INSTALL_PATH>/_uninst/uninstall program.
Follow the instructions on screen to complete the uninstallation of Alliance Web Platform
Server-Embedded.
5.2 Silent Removal

Prerequisites
The response file must be available.
Silent uninstallation of the Alliance Web Platform Server-Embedded software

2. Type the following command in the command prompt:

<SWP_INSTALL_PATH>/_uninst/uninstall -silent <path to the response file>
Removal
5.3 Next Steps

5.3.1 Other Tasks
Procedure
1. If automatic startup is set for the Alliance Web Platform Server-Embedded (as described in
the Alliance Web Platform Administration and Operations Guide), then it must be manually
removed.
2. Delete the default path Alliance/WebPlatform/ in the installation directory.
3. Re-start your system.
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
6 Patches
6.1 Install Patches

Introduction
Software fixes are applied in the form of patches. There are two types of 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:
1. Make sure that the Alliance Web Platform server is running.
2. Back up all data and software.
3. Read the patch release letter carefully. It describes the scope of the patch and the
installation instructions.
For cumulative patches:
A cumulative patch can be installed on a base release, on a previous cumulative patch, or on

a previous optional patch. A cumulative patch contains all cumulative and optional patches
since the base release.
For optional (emergency) patches:
An optional patch can be installed on a base release, on a previous cumulative patch or on a

previous optional patch. You must install optional patches in chronological order as specified
by their release number. For example, install release 7.0.1, then 7.0.2, and then 7.0.3.
Removing an optional patch restores the previous version of the affected deliverables.
For all 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.
Prerequisites to upgrade from Alliance Web Platform Server-Embedded 7.0.40/7.0.50

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.
Patches
6.2 Remove Patches

Can the patch be removed?
Not all patches can be removed. Patch 7.0.60 can not be removed.
Prerequisites
Make sure that the Alliance Web Platform server is running.
See the patch release letter for specific uninstallation information.
27 March 2015 31
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.
7.2 Error Messages

Troubleshoot error messages during installation
If errors occur during installation, then check the following:
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.
Launch the checkhost again to check the system requirements.
If you are using a hosted database, then check the prerequisites again.
Troubleshoot error messages after installation

If errors occur after installation, then do the following:
Check the event log of Alliance Web Platform Server-Embedded with Alliance Web Platform
Administration or execute swp_readlog in the command prompt.
If possible, check the connection of the database. Execute swp_config -packages -

list.
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:
<host> is the hostname where Alliance Web Platform Server-Embedded is installed
<port> is the port number
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
8 Additional Information
8.1 Non-root Installation

Purpose
It is possible to install or patch the Alliance Web Platform Server-Embedded software with a
non-root user account. The non-root user account will own the installation.
A non-root user logs on using the owner account and launches the installer to begin the
installation. Before you can launch the installation with a non-root user account, you must
perform specific pre-installation steps.
Overview of a non-root installation
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.
8.2 Silent Operations

Difference between silent operations and interactive operations
The difference between interactive and silent operations is the way input data is provided. In an
interactive procedure, this data is provided through a series of windows. In a silent operation,
the data is provided in a response file. For more information, see "Response Files
Configuration" on page 35.
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.
Additional Information
Scope
The following Alliance Web Platform Server-Embedded operations can be performed silently:
Installation
Removal
Patch installation
Patch removal
8.2.1 Response Files Configuration

8.2.1.1 Response Files
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.
Create a response file

You can prepare a response file in the following ways:
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).
Record input parameters

If the -record option is provided as an option during installation, upgrade or removal, then the
program will perform the follow actions:
Create a response file in the location specified.

If a file of the same name already exists, then it is overwritten.
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
8.2.1.2 Response File Parameters
Purpose
This section describes the possible parameters and indicates their applicability in installation-
related operations.
Parameters table - notational convention

The following syntax applies:
M = mandatory parameter on all platforms.
(M) = parameter that is mandatory if the database is hosted on an external machine.
O = optional parameter on all platforms. If the parameter is not specified, then the default
value is used.
- = not relevant.
To make passwords non-readable

When launching a silent installation, the passwords can be made non-readable in the response
file. The parameters that end with .encrypted must be used to provide encrypted or
obfuscated values only. For more information, see "Protect the Passwords in the Response
File" on page 17.
Response file parameters

The following table lists the parameters that must be defined in the response file for Alliance
Web Platform Server-Embedded:
Installation
Removal
Upgrade
Parameter Description
system.installOption Type of installation. M M -

Use base (installation) or
delta (upgrade)
system.deinstallOption Uninstall type - - M

Use base (full system
removal), or delta (patch
removal).
application.key A keyword that identifies the swpe swpe -

product
Mandatory.Accept.LicensingTerms Licensing agreement. Must M M -

have the value: Agree
application.installLocation Installation directory M M -

Use "/" character as escape
character for ":" or "/"
characters.
For example, ./Alliance/
WebPlatform70 should
be .//://Alliance//
WebPlatform70
Installation
Removal
Upgrade
application.instanceName Name of the instance M - -
application.ipAddress IP address of the machine M - -

where the instance is installed
This parameter is defined
when the database is
embedded.
application.owner.name Operating system account M - -

that is the owner of the
resulting instance
database.type The type of the database. Use M - -

the value embedded, or
hosted.
oracle.listener.host Mandatory for hosted (M) - -

database:
Host name of the server on
which the database is
installed.
oracle.listener.port Mandatory for hosted O, - -

database: (M)
Port number that is used to
connect to the Alliance Web
Platform Server-Embedded
database.
If not defined, then the default
port number is used: 1521
oracle.sid Mandatory for hosted (M) - -

database:
The Oracle service ID of the
hosted database.
database.schema.name Mandatory for hosted (M) - -

database:
Database schema owner
name.
database.schema.password Mandatory for hosted (M) - -

database.schema.password.encrypted database:
Password for the database
schema owner.
database.user.name Mandatory for hosted (M) - -

database:
Database user name to be
used by the application server
to connect to the database.
database.user.password Mandatory for hosted (M) - -

database.user.password.encrypted database:
Password for the database
user name.
swp.administrator.name Administrator of the Alliance O O -

Web Platform Server-
27 March 2015 37
Installation
Removal
Upgrade
Embedded. If not specified,
then the administrator
account name is set to:
swpadmin.
swp.administrator.password Password assigned to the M M -

swp.administrator.password.encrypte administrator of the Alliance
d
Web Platform Server-
Embedded.
oc4j.listener.host Host name used in URLs to M - -

access Alliance Web Platform
Server-Embedded.
oc4j.listener.port Port number used in URLs to O - -

access Alliance Web Platform
Server-Embedded. If not
defined, then the port number
is set to: 2443.
oc4j.rmi.port Port number used internally O - -

by Alliance Web Platform
Server-Embedded for
listening on RMI requests. If
not defined, then the port
number is set to: 23991.
oc4j.admin.port Port number used internally O - -

Server-Embedded for admin.
If not defined, then the port
number is set to: 23992.
oc4j.jmx.port Port number used internally O - -

Server-Embedded to listen for
JMX requests. If not defined,
then the port number is set to:
23993.
8.3 Check Your System Configuration

Uses of the checkhost tool
You can use the checkhost tool provided on the Alliance Web Platform Server-Embedded
installation media to analyse the configuration of a computer and produce a report from the
results. The tool can provide the following output:
A full system analysis report.
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.
8.3.1 Launch the checkhost Tool

Procedure
1. Log on as root.
3. Navigate to the directory that contains the tool.
4. Launch the checkhost tool. See "checkhost Syntax and Examples" on page 39 for
syntax information.
8.3.2 checkhost Syntax and Examples

Syntax
./checkhost.ksh
checkhost [-req <pathname of requirements file>]
[-rootdir <pathname of a directory>]
[-out <pathname of the report file>]
[-outxml <pathname of file containing report in XML format>]
[-stdout <checkhost report will be flushed to stdout>]
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
8.3.3 The Full System Analysis Report

Report specifics
When running the checkhost tool without specification of a requirements file, the following
report details are produced:
Information Unit Reported?
Checkhost command invoked Yes
CPU type Yes
CPU speed(1) MHz Yes
Number of CPUs Yes
Memory size(2) MB Yes
OS version Yes
OS patch level Yes
Local hostname Yes
Free disk space MB Yes
Installed software Yes
Installed patches Yes
Network adapters(3) Yes
IP addresses Yes
File systems Yes
Paging space MB Yes
Kernel boot Yes
Kernel width Yes
Installed devices Yes
OS language No
Local time zone Yes
DNS server Yes
Network options(4) Yes
(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.
8.3.4 The Comparative Analysis Report

Introduction
The comparative report indicates whether a given host machine passes the requirements
criteria in a requirements file.
Performing a comparative analysis before a software installation ensures that the intended host
machine meets the requirements.
Requirements file
The following requirements file is found on the Alliance Web Platform Server-Embedded media.
File Name Description
systemtest.dat Contains the base requirements for Alliance Web Platform Server-Embedded
installation.
8.4 Upgrading the Operating System for Alliance

Web Platform Server-Embedded (Embedded
Database)
Overview
Use the following procedure to upgrade your operating system version or to migrate your
Alliance Web Platform installation to new hardware. The procedures that follow assume that you
are installing your new operating system version from scratch as a fresh installation.
Procedure
1. Use swp_config -packages -list to check the Alliance Web Platform patch level.
2. Use swp_backup <file_pathname> to make a backup of the configuration.
3. Use swp_config -exportcert -keystore <filename> to make a backup of the

certificate (patch 7.0.50 and higher).
4. Install the new operating system version.
5. Install Alliance Web Platform 7.0 (or any other base release such as 7.0.50 or 7.0.60).
6. Upgrade Alliance Web Platform to the same patch level as before.
7. Use swp_restore <filename> to restore the configuration.
8. Use swp_config -importcert -keystore <filename> to restore the certificate.
9. (Optional) Upgrade Alliance Web Platform to a newer patch level.
27 March 2015 41
8.5 Upgrading the Operating System for Alliance

Web Platform Server-Embedded (Hosted
Database)
Overview
Use the following procedure to upgrade your operating system version or to migrate your
Alliance Web Platform installation to new hardware. The procedures that follow assume that you
are installing your new operating system version from scratch as a fresh installation.
Procedure
1. Use swp_config -packages -list to check the Alliance Web Platform patch level.
2. Use swp_config -exportcert -keystore <filename> to make a backup of the

certificate (patch 7.0.50 and higher).
3. Install the new operating system version.
4. Create a "dummy" database schema that will be deleted later.
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.
6. Upgrade Alliance Web Platform to the same patch level as before.
7. Use swp_config -importcert -keystore <filename> to restore the certificate.
8. Use swp_bootstrap stop to stop the application server.
9. Use swp_config -hosteddb to change the database parameters to point to the original
schema.
10. Use swp_bootstrap start to start the application server.
11. Use swp_config -syncdb to synchronize the database to load the installed packages in
the application server.
12. Delete the "dummy" database schema.
13. (Optional) Upgrade Alliance Web Platform to a newer patch level.
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

Awp Serv Embedded 7 0 60 Inst Guid Aix PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Awp Serv Embedded 7 0 60 Inst Guid Aix PDF

Transféré par

Droits d'auteur :

Formats disponibles

AIX

Alliance Web Platform Server-Embedded 7.0.60

1 Installation Features Overview ................................................................................................................. 5

8 Additional Information ................................................................................................................................ 34

Alliance Web Platform Administration and Operations Guide

1 Installation Features Overview

Hosted database or embedded database

Recording the installation

Performing actions as a non-root user

What SWIFT delivers

2.1 Alliance Web Platform Server-Embedded

2.1.1 Communication Protocols and Ports

Communication link Protocol Default port

Browser - Alliance Web Platform/Administration HTTPS 2443

Note Alliance Message Management uses SwTL and SOAP.

2.2 Roles in Alliance Web Platform and Management

2.2.1 Alliance Web Platform Owner

2.2.2 Alliance Web Platform Users

2.2.3 Alliance Server Users

3.1 Getting Started

3.2 System Requirements

Requirement Disk space requirement

Temporary files for program installation 1,200 MB in /var/tmp/

Target installation directory for embedded 5,000 MB minimum; 10,000 MB recommended

Target installation directory for hosted database 1,024 MB

A Korn shell is required.

Only a 64-bit kernel is supported.

The hardware processor must have 64 bits.

Alliance Web Platform Server-Embedded installers are graphical applications. A dedicated X

Note A X display terminal is not needed if you run a silent installation.

3.3 Hostname Resolution

3.4 Create the Alliance Web Platform Owner Account

Create the sagsnlg group

3.5 Modify Process Resource Allocation

3.5.1 Ulimit Settings

Setting Parameter name Value

Coredump core Unlimited

Data data Unlimited

File fsize Unlimited

Memory rss_hard Unlimited

Nofiles nofile 4096

Processes nproc Unlimited

Stack stack Unlimited

Time cpu Unlimited

Edit ulimit settings

3. Save the file.

Verify the ulimit settings

2. Run the following command:

The output must be similar to the following:

3.5.2 Ephemeral Ports Settings

2. Update the script /etc/rc.tcpip with the following lines:

3.5.3 dev_attributes Configuration

2. Turn off AIX 4.3 core generation.

3. Change the ncargs value.

4. Change the maxuproc value.

5. Reboot your system.

To verify the kernel parameters

2. Run the following commands to verify the kernel parameters.

3.6 Web Browser Settings

2. Select the General tab.

3. Click Settings in the Browsing history section.

4. Set the Check for newer versions of stored pages to Automatically.

6. Select the Advanced tab.