The user can choose to install a new instance: Enter "i" to launch the interactive installation.
Welcome to the DUAS installation procedure
...
=========================================================================
Starting installation in interactive mode.
# -----------------------------------------------------------------------
The installation dialog lists the following topics:
# AUTOMIC license agreement:
# Please, read AUTOMIC license agreement, press <space bar> to read next page
# Press return to continue
[Return] advances line by line, [Space bar] advances page by page.
Do you accept the agreement ?
--> ("y" to accept, "n" to decline and abort procedure)? y
=========================================================================
Enter "y" if you accept the terms of the USLA. If you do not accept the USLA ("n"), this will cancel the installation.
Your installation has been done with the user "root".
if you want to administrate this instance with another user than "root",
Give the already existing username, by default root user will be administrator [root] :
This option allows you to assign instance files to another owner than "root". However, batches can be submitted by any user account including "root" and the instance will benefit from starting automatically.
This is different from the installation under a different account than root.
If the instance is installed under another user account than root, the instance files belong to that user, auto-start is not configured and batches can only be submitted by the user account.
=========================================================================
Do you want to install a cluster node ("y" or "n")? [n] :
=========================================================================
By default "n" will proceed with a standard local installation. If a cluster installation is required:
UNIX Primary Cluster Node
Do you want to install a cluster node ("y" or "n")? [n] : y
To install a cluster correctly, logs and root/data folders must be installed on a disk shared by all cluster nodes.
The binaries folder can be installed locally or in a shared folder.
Do you want to install a primary or secondary cluster node ("s" or "p")? : p
Refer to the Dollar Universe Administration Guide for more detailed discussion of Dollar Universe Cluster Architectures.
In an Active-Passive cluster only one node is active.
On the primary node, a full Dollar Universe instance is installed on a shared disk.
Selection of the Primary Cluster Installation sets the variable "UNI_INST_CLUSTER=PRIMARY" in the local settings (…\data\values.xml).
Do you want to install a primary or secondary cluster node("s" or "p")? : s
The secondary node will be installed with information collected from the primary node installation.
Enter the path to the "values.xml" file from the primary installation:
The secondary node must be installed after the primary node as it needs access to the "values.xml" generated by the primary node installation.
If the shared disk on which the primary node was installed cannot be switched to the secondary node, the values.xml file should be copied to a work directory. The file is necessary just for the installation phase.
No data is installed, only binaries are installed in a similar folder as the primary node and only if the binary folder has not been installed in a shared folder upon installation of a primary node.
If there is a shared binaries folder, the folder must be reachable by the secondary node during installation.
Registration requires you to provide the hostname of the Univiewer Management Server (the name must comply with RFC 952), the TCP port number used by the Management Server (default =4184), the administrator login and password specified during the installation of the Univiewer Management Server.
You have to register on a Univiewer Management Server (UVMS). This can be done later but this is not recommended.
Do you want to register to the UVMS now? [y] :
UVMS registration information:
------------------------------
Univiewer Management Server hostname : <hostname>
Univiewer Management Server port number [4184] :
Univiewer Management Server administrator login ID [admin] :
Univiewer Management Server administrator password : xxxxxx
executing command :
./unims ...
UVMS on <hostname>/4184 reachable, version 6.x.yy
Univiewer Management Server is reachable.
This phase checks the connectivity of the Univiewer Management Server, connection to the UVMS will be verified with the values entered and an error message will be displayed if any of the values prove to be incorrect or if, in the case of a central license, the maximum number of nodes is exceeded.
If for some reason the Univiewer Management Server is unreachable at the time of installing the Dollar Universe Application Server, you can register manually with the unims command shown above. Refer to section "Register Manually to UVMS" for details about the unims command.
The node name by default assumes the value of the local hostname. It is limited in length to 64 alphanumeric characters. The node name in Dollar Universe Application Server V6 is however a free identifier.
DUAS Company name [UNIV65] :
DUAS Node name [<hostname>] :
executing command :
./unims ...
Couple node/company is validated by UVMS.
Multiple instances of the same Company can be installed on the same host on condition that the Node name is unique. Installation will be refused if the Company-Node name couple has already been registered on the Univiewer Management Server.
The .Installer subdirectory in /var/opt/ORSYP contains details of instances already installed on the machine. This is particularly useful for the uninstallation process.
Node Tags are free text identifiers that characterize a node. If you specify a Tag that is included in a Node View, the DUAS being installed will be dynamically included in the corresponding Node View for operations monitoring.
DUAS node tags :
No default values are provided. Input is optional.
The Dollar Universe Application Server hostname by default is the same as the local hostname. But in cluster configurations the Dollar Universe Application Server Hostname may be a logical identifier permitting TCP Access. The name must comply with RFC 952.
Change the "DUAS hostname" only if you need to set a different logical network name
(useful for cluster configuration).
DUAS hostname [<hostname>] :
By default the instance directory is /var/opt/AUTOMIC/DUAS/<COMPANY>_<node>.
The instance's root directory is accessible via the environment variable ${UNI_DIR_ROOT> which is set in the unienv.ksh procedure.
DUAS Root directory (full path) [/var/opt/AUTOMIC/DUAS/<COMPANY>_<NODE>] :
In the case of a primary cluster node, the root directory should be located on a shared disk.
In the case of a secondary cluster node the root directory should be located on a local disk.
Each DUAS contains four environments called Areas corresponding to the operations life cycle, starting with the initial development of operations procedures (Application Area) through various phases of test (Integration Area) and pre-production (Simulation Area) before go live in the Production Area.
All four Areas will not be necessary on every instance, by default only the Production Area is activated. Areas can be enabled after installation with the unims command, refer to section "Upgrade".
By default only the Production area (X) is deployed.
Others areas: Integration (I), Simulation (S) and Application (A) can be configured.
Do you want to configure these areas now? [n] : y
Do you want to configure DUAS Application Area (A)? [n]:
Do you want to configure DUAS Integration Area (I)? [n]:
Do you want to configure DUAS Simulation Area (S)? [n]:
Some Managers are integrated with Dollar Universe. They can be installed and activated or deleted during installation.
By default, all available DUAS managers in this package will be installed but not yet activated (i.e. kept).
You can also choose to remove or activate a manager (i.e. installation + registration on UVMS).
Do you want to manage installations of any DUAS managers ("y" or "n")? [n] : y
Choose the answer "y" to intervene in the installation of one or more Managers. If you answer "n" go straight to the next paragraph.
Usage of Manager for SAP Solutions
Selecting "remove" will remove the possibility to use the manager in the future without reinstallation.
You can provide an already defined configuration file or configure one later.
Do you want to remove(r), keep(k) or activate(a) the manager for SAP solutions ("r", "k" or "a", default is "keep")? [k] : a
Depending on the selected Manager, additional information may be requested:
You can provide an already defined configuration file or configure one later.
If you have already defined a configuration, give the full path of the folder containing your "uxjcs.ini" file, or hit return? :
Default configuration file will be used.
Entering the uxjcs.ini configuration file is optional; it can be done later using the Univiewer Interface Console.
Prerequisites must be met to install or upgrade Dollar Universe Manager for SAP Solutions; please refer to section "Software".
Usage of Manager for Oracle Applications
Selecting "remove" will remove the possibility to use the manager in the future without reinstallation.
You can provide an already defined configuration file or configure one later.
Do you want to remove(r), keep(k) or activate(a) the manager for Oracle Application ("r", "k" or "a", default is "keep")? [k] : a
You can provide an already defined configuration file or configure one later.
If you have already defined a configuration, give the full path of the folder containing your "uxoapp_db_user.xml" file, or hit return ? :
Default configuration file will be used.
Entering the uxoapp_db_user.xml configuration file is optional; it can be done later using the Univiewer Interface Console.
Usage of the ODB, EJB, JMS, WSC Managers
If you won't use one these managers, select the remove switch "r",this will remove the possibility to use the corresponding manager(s) in the future without reinstallation.
If you may use one of these managers, select the "k", to keep possibility to activate it later.
If you are sure to use one of these managers, select the "a", to (pre)activate the usage of the(se) manager(s).
Selecting "k" or "a" will require a post-configuration from the console to fully activate the corresponding manager(s).
Make your choice concerning these managers: ODB, EJB, JMS, WSC ? ("r(emove)", "k(eep)" or "a"(ctivate), default is "keep")? [k] : a
You must provide the path of a valid "java" command (version >= 1.6).
Give the full path of the command [/usr/bin/java] :
Default port numbers can be provided by your Univiewer Management Server,
or you may set them yourself.
Do you want to use default port numbers? [y] :
executing command :
./unims ...
Ports set is validated by UVMS.
Dollar Universe reserves 19 consecutive TCP port numbers. The default range starts at 10600 (base port number) and is attributed as shown in the table below:
|
Espace |
IO |
EEP |
BVS |
SAP | OAPP (UNIX) |
CDJ |
DQM |
JEE |
GSI |
|---|---|---|---|---|---|---|---|---|---|
|
X |
10600 |
10604 |
10605 |
10609 | 10610 |
10611 |
10615 |
10616 |
10618 |
|
S |
10601 |
|
10606 |
10612 |
|
|
|||
|
I |
10602 |
|
10607 |
10613 |
|
|
|||
|
A |
10603 |
|
10608 |
10614 |
|
|
In a default installation only the Production Area (X) is enabled, in this case only ports 10600, 10604, 10605, 10611, 10615 and 10618 are actually used.
If the sequence 10600 to 10618 is unavailable, enter an alternative base port number (with the 19 free consecutive TCP port numbers).
You must ensure that any firewall on the path to/from the DUAS is correctly configured to allow communication between the selected DUAS and UVMS ports.
Example: If the sequence 10600 to 10618 is unavailable:
Do you want to use default port numbers? [y] : n
You will need to declare 11 tcp/ip port socket numbers.
Enter the DUAS TCP port base number : 12600
Port for IO server of Production area (X) will be : 12600
Port for Business Views Server of Production area (X) will be : 12605
Port for CDJ Production area (X) will be : 12611
Port for DQM server will be : 12615
Port for Supervisor server will be : 12604
Port for Generic Integration Server will be : 12618
Port for manager for Sap Solutions : 12609
Port for manager for Oracle Application : 12610
Port for Java manager : 12616
Port for IO server of Application area (A) will be : 12603
Port for Business Views Server of Application area (A) will be : 12608
Port for CDJ Application area (A) will be : 12614
The number of ports reserved depends on the number of Areas and Managers activated.
It is no longer required that nodes within the same Company share the same TCP port sequence to be able to communicate. Node information is maintained centrally on the UVMS and regularly synchronized across all Dollar Universe Application Servers. Refer to the Dollar Universe Administration Guide for more details about synchronization.
Default Binaries Dialog
You can share binaries with another DUAS instance.
This option is useful for upgrading all your instances at the same time, in this case:
1) All instances must have the same version level.
2) If you want to share binaries with another instance, it is best to select a directory outside of this instance's directory structure.
3) If the shared directory already exists, enter the existing path.
4) For the first shared instance installation, the directory must not exist, it will be created with a "bin" subfolder.
If you want a standard installation, use the proposed default path for your binaries directory.
Enter the full path to the binaries directory [/var/opt/AUTOMIC/DUAS/<COMPANY>_<NODE>/bin] :
Using a new non shared Executables folder.
By default the bin subdirectory is created, and the binaries will be loaded under the installation directory in:
/var/opt/AUTOMIC/DUAS/<COMPANY>_<node>/bin
Shared Binaries Dialog
If you wish to share binaries with multiple instances, specify a directory outside the structure of your instance that does not exist.
Example
Enter the full path to the binaries directory [/var/opt/AUTOMIC/DUAS/<COMPANY>_<NODE>/bin] :
/DUAS_Common/bin
Using a new non shared Executables folder.
Successive installations sharing the same binaries will display the following message:
Use of an existing and shared Executables folder.
You may also wish to position the log directory outside of the instance structure. Log files tend to expand rapidly when problems occur, so positioning them in file systems where lack of space can do the least harm is probably a good idea.
You may define a separate directory for log files.
This directory must not exist, it will be created with a "log" subfolder.
Enter the full path to the log directory [/var/opt/AUTOMIC/DUAS/<Company>_<Node>] : /orsp/<Company>_<Node>
Installation is going to start...Press return to continue or Ctrl C to abort
The installation actually begins at this step.
Example:
===========================================================================
DUAS instance has been installed successfully.
===========================================================================
===========================================================================
Registering the DUAS instance to the Univiewer Management Server :
===========================================================================
===========================================================================
Registration of DUAS instance to Univiewer Management Server FRWPMDEV08
===========================================================================
--> executing : /var/opt/AUTOMIC/DUAS/UNIV65_vmstluni99.automic.com/bin/unims -register -login admin -pwd xxxxxx -mgrSAP
passphrase=<b9f9II=<T4@@=_aC1Hdw>
12 ports received.
<IO > A = 12603
<BVS> A = 12608
<CDJ> A = 12614
<IO > X = 12600
<BVS> X = 12605
<CDJ> X = 12611
<DQM> X = 12615
<EEP> X = 12604
<GSI> X = 12618
<SAP> X = 12609
<OAP> X = 12610
<JEE> X = 12616
1 UVMS host received.
[FRWPMDEV08:4184]
Registration with UVMS FRWPMDEV08_MgtServer (FRWPMDEV08/4184) successful.
The registration of DUAS on the Univiewer Management Server ends with success.
===========================================================================
============================
Instance registered.
============================
DUAS environment loaded for Company UNIV65 Node vmstluni99.automic.com.
===========================================================================
Starting DUAS instance with the command:
"/var/opt/AUTOMIC/DUAS/UNIV65_vmstluni99.automic.com/bin/uxioserv UNIV65 X vmstluni99.automic.com"
===========================================================================
...
# -------------------------------------------------
# DUAS instance is started.
# -------------------------------------------------
End of installation with success.
Installation log file is /var/opt/AUTOMIC/DUAS/UNIV65_vmstluni99.automic.com/log/orsyp_installation.log