Installing the Central Designer application server (2.1)

Locate the setup.exe program.
The setup.exe program is available the Oracle Software Delivery Cloud (https://edelivery.oracle.com).
Double-click setup.exe.
The InstallShield Wizard prepares to install the application server.

A welcome page appears.
Click Next.
The Customer Information page appears.
Provide the following information:
- User Name —Your name.
- Company Name —The name of your company.
- Company URL —A unique identifier for your company data, typically your company URL (for example, http://www.mycompany.com).
- Select whether to install the application for anyone who uses the computer, or only for your user.
Click Next.
The following page appears.
Select New Database.
Note: If you are installing the second or higher server in a web farm, do not select New Database. You must select Update.
In the Destination Folder area, specify the destination location for the installation. By default, the installation wizard installs the software in the < PROGRAMFILESDIR>\Oracle Health Sciences\Central Designer\ folder. PROGRAMFILESDIR is a system setting that is usually C:\Program Files. If you want to install to another location, click Browse, and select the location.
Note: The instructions, paths, and Start Menu navigation in this guide assume you are installing to the default location. Oracle strongly recommends that you install the software to the default location.
Click Next.
The following page appears.

Fill in the fields in the page as follows.

Field	Description
Database User Name	The Oracle user name for the database user.
Database Password	The password for the database user. Note: The password must not contain any of the following characters: @ & ( ) [ or ].
Oracle TNS Name	Alias from the TNSnames.ora file. This TNS name is used to connect to the database instance.
Database Administrator User Name	The Oracle user account for the database administrator. This account is used to create the database user. Note: The user name cannot be a SYSDBA user account.
Database Administrator Password	The password for the database administrator. Note: The password must not contain any of the following characters: @ & ( ) [ or ].
Create New Database	Indicate whether to create a new database schema during installation. Caution: If you have an existing database schema and you select Create New Database, all existing information in your current database schema will be deleted .

Note: Do not use Oracle reserved words for user names or passwords.

If a new database was created and tablespaces were created with non-default names, you must specify the names of the tablespaces. The tablespaces that you specify must already exist. The installation does not create tablespaces.

Click Advanced.
The Advanced Database Settings page appears.
Fill in the fields with the correct information, according to the following table.

Click OK to return to the Database Parameters page.

Field	Description
Default Tablespace for new user	The first tablespace for the tables of the schema owner. For an Oracle 12c database, this tablespace must have a block size of 16k.
Large (16K) Tablespace for new user	A second tablespace with a block size of at least 16k. Note: This tablespace is not required for Oracle 12c databases.
Temp Tablespace for new user	The temporary tablespace for the tables of the schema owner.

Field

Description

Default Tablespace for new user

The first tablespace for the tables of the schema owner.

For an Oracle 12c database, this tablespace must have a block size of 16k.

Large (16K) Tablespace for new user

A second tablespace with a block size of at least 16k.

Note: This tablespace is not required for Oracle 12c databases.

Temp Tablespace for new user

The temporary tablespace for the tables of the schema owner.

Click Next.
The following page appears.
Enter the TCP/IP port number that the job service will use. The port must be unused. In most cases, you can use the default value.
Note: If you are installing the server as part of a web farm, all of the servers can use the same port number, as long as the port is unused.
Optionally, to configure the Central Designer software to support a web farm, select Make this server part of a web farm. A web farm setup allows you to install the Central Designer server software on multiple application server computers. The installation is the same for all of the servers, and you must select this option for all servers in the web farm. For more information, see Web farm capabilities.
After you select the checkbox, the installation checks the database to see if a primary Job Scheduler has been specified. Additional options appear, depending on whether you are installing the first or second (or higher) server.
- If this installation is the first server in the web farm, the primary Job Scheduler has not been set yet. The installation automatically sets the Job Scheduler service on the server computer as the primary Job Scheduler. If you install additional application servers, you can change the primary Job Scheduler during the installations.
- If this installation is the second or higher server in the web farm, the primary Job Scheduler service has already been set, and the name of the computer that runs the primary Job Scheduler appears. To change the primary Job Scheduler, select Make this server's Job Scheduler the primary.
Specify a password for the Job Service user.
Note: Make sure that the user password meets the requirements listed on the page.
Click Next.
The following page appears.
Specify a password for the system user.
Note: Make sure that the user password meets the requirements listed on the page.

The Central Designer application installs the system user by default. You can configure the lockout time for the system user separately from all other users. By default, this user is assigned the superuser and DesignerAdministrator roles.

Note: The password that you specify for the system user is also used for the archiveimporter user. For more information about this user, see the Administrator Guide.
Click Next.
The Network Parameters page appears.
In the Web server URL root field, enter the server address to which requests will come (for example, http://ABCServer or https://ABCServer ). If you enabled Transport Layer Security (TLS), use https .
Note: When the application server is installed in an environment that includes a hardware networking switch, the URL that you enter for the Web server URL root field must match the URL that the networking switch uses to address the application server. For more information, see Hardware networking switches.

As you enter a value in the Web server URL root field, the Public server URL root field is automatically updated with the same value. If you edit the value in the Public server URL root field, the field is no longer updated automatically when the Web server URL root field is updated.
Optionally, you can secure (encrypt and prevent tampering of) communications by using Transport Layer Security (TLS). For more information, see Securing communication with Transport Layer Security (TLS).
Optionally, if the application server computer is behind a proxy that rewrites the request URLs, in the Public server URL root field, enter the address that the client computer uses to access the application server (the public address of the server computer as seen by the client computer). This address will be added as the address of the server computer during installation of the client applications.
If the value for the Public server URL root field does not need to be different from the Web server URL root field, make sure that the values in both fields match.
Specify the certificate to use to sign web service authorizations:
1. Click Choose Certificate.
  The Choose Certificate dialog box appears.
2. Select a certificate.
3. Click OK.
  The Issued to, Issuer, Expiration, and Friendly name fields are populated.
Note: On each Central Designer application server, an administrator must install the certificate that is used for signing web service authorizations to the LOCAL_MACHINE\MY store. The Central Designer installation process grants Full Control to access the certificate private keys to the IIS AppPool\DefaultAppPool user and the NETWORK SERVICE user.

If a user other than the IIS AppPool\DefaultAppPool user is running the DefaultAppPool application pool, you must grant the user Full Control to access the private keys, or the user is unable to sign using the certificates. For more information, see Installing certificates for signing web service authorizations and deployment packages.
If the Central Designer application server is outside the network of the InForm application server. Specify the proxy URL or script used by the Central Designer application server to communicate with the InForm server during automated deployment:
- In the Proxy URL field, enter the web address for the proxy server.
- In the Proxy Script field, enter the web address for the proxy configuration script.
Click Next.
The Client Installation Configuration page appears.
In the Environment Name field, enter the name for your Central Designer instance.
The environment name appears on the web page to which you navigate to start the Central Designer application.
Click Next.
The InForm Deployment page appears.
Specify the certificate to use to sign deployment packages and InForm web service authorizations:
1. Click Choose Certificate.
  The Choose Certificate dialog box appears.
2. Select a certificate.
3. Click OK.
  The Issued to, Issuer, Expiration, and Friendly name fields are populated.
Note: For studies hosted by Oracle Cloud for Industry, the certificate must be issued by a trusted commercial Certificate Authority.
Click Next.
The Start Copying Files page appears.
Review the installation settings. To change any settings, click Back. If you are satisfied with the settings, click Next.
The installation begins. The Setup Status page appears, showing the status of the installation.

When the installation is complete, the InstallShield Wizard Complete page appears.
Click Finish.

Note: If the IIS worker process is running under any user other than NETWORK SERVICE or IIS AppPool\DefaultAppPool, you must grant the user read permission to the HKEY_LOCAL_MACHINE\SOFTWARE\OracleHS\CentralDesigner registry key after the installation.