Setting up the installation server on Linux®

Applies to:

You can set up the installation server on a server in your deployment or on a separate computer. Use a computer that can communicate with the servers in your OpenPages® environment.

After you set up the installation server, you can use the OpenPages installation app to create and manage deployments.

Important: If you use Windows servers in your deployment, set up the OpenPages installation server on a Windows computer. See Setting up the installation server on Windows.

Note: If you already set up the installation server and you want to update it with a fix pack, see Update the installation server and agents with a fix pack.

Before you begin

The computer where you set up the installation server must meet the following requirements:

IBM® Semeru Runtimes is installed.
Java™ is included in the PATH system environment variable.
JAVA_HOME is set.

You might also want a PDF reader application on the computer. When you install or upgrade OpenPages, you can download validation reports in PDF format.

About this task

This video demonstrates how to set up the installation server. The steps are similar for 9.2.x:

Procedure

Log on to the computer as an administrator.
If an earlier version of the installation server is running, stop it.
Do one of the following steps:
- Update the antivirus policy on the installation server computer to allow Node.js.
- Disable antivirus software on the installation server computer. You can re-enable it after you install the installation server.
Create a directory.
If you have more than one version of the installation server on the same host, use a separate directory for each version.
For example, /home/opuser/IBM/OPInstall<version> .
Locate the installation files.
The files are stored in /OP_<version>_Main/OP_<version>_Installer.
Copy the contents of the OP_<version>_Installer directory to the directory that you created.
Change directory to /home/opuser/IBM/OPInstall/OP_<version>_Installer/install/Linux.
Grant the +rwx permission to the user on the installation server directory, subdirectories, and scripts.
Open a shell and run the setup script.
You can use the following optional arguments:
- -p <password> – Sets the password for the initial installation app user, called admin. If you exclude the argument, the install.bat script prompts you for the password.
- -n <port> – Sets the port that the installation server runs on when you start it. If you have multiple installation servers that run on the same hardware, ensure that each installation server uses a different port number. Specify an integer in the range 0 - 65535. If you exclude this argument, the default port number (8443) is used.
- -m <old_directory> – Migrates existing deployments and installation server user accounts to the new installation server. Use this argument if you have existing deployments that you want to use with the new installation server. For <old_directory>, enter the full path to the existing installation server home directory. Alternatively, you can migrate deployments and users after you install the new installation server. For more information, see Migrating deployments and installation server users.
- -s – Prevents the installation server from starting after the install.sh script completes. If you exclude this argument, the installation server starts automatically after the install.sh script completes.
Syntax:
```
./install.sh –-acceptLicense [-p password] [-m <old_directory>] [-n <port>] [-s]
```
If you did not use the -p parameter, type a password and then press Enter.
Close the shell window.
After the installation completes, re-enable the antivirus software on the installation server.
Do this step if you disabled the antivirus software in step 3.
Update the installation server to the latest fix pack version.
See Update the installation server and agents with a fix pack.

Results

The OpenPages installation server is installed.

If you used the -s argument, start the installation server. For more information, see Starting the installation server.

You can now log in. For the user name, type admin. For the password, type the password that you set when you ran the install.sh script. For more information, see Logging in to the installation app.

Note: If you used the -m argument but some deployments or users were not migrated, do not run the install.sh script again. Instead, repeat the migration without reinstalling. See Migrating deployments and installation server users.