Clustered deployments - assure_dq

If you have a clustered deployment, refer to the topics in this chapter that are applicable to your application server.

Requirements for a clustered deployment

The following environment requirements apply to clustered deployments:

Shared file system—All cluster members must have access to the following shared folders:
- Precisely CONFIG_HOME folder, for the Precisely application configuration properties, where CONFIG_HOME is the location defined by this property.
- Precisely DATA_HOME folder, for file-based data and the current state of the internal clock, where DATA_HOME is the location defined by this property.
- Precisely JDBC_HOME folder, for the JDBC drivers, where JDBC_HOME is the location defined by this property.
- Precisely ARCHIVE_HOME folder, for archived files, where ARCHIVE_HOME is the location defined by this property.
- Precisely DIAG_HOME folder, for diagnostic files in WildFly, where DIAG_HOME is the location defined by this property.
- Precisely DATA_TEMP folder, for temporary files generated by your Precisely application, where DATA_TEMP is the location defined by this property.
- For Insight, REPORTS_FOLDER in which ACR reports are stored, where REPORTS_FOLDER is the location defined by this property.
Synchronized system clocks for all cluster members, achieved by using a clock sync service.
Router support for IP multicasting.
You will have to customize certain properties beyond the default configuration. The properties that you must edit will vary, depending on your environment. Open each property file and change the values. See the sections below for each property file.

Tip: You do not have to specify any property values that begin with $. During the deployment process, the system will determine the values for these properties. For detailed information about property values, see the Properties Guide.

Enable HTTPS requests between products

In a clustered environment, where two or more Precisely applications are integrated, you will have to configure certain properties to enable secure connectivity.

Navigate to the httpinvokeserver.properties file:


<install_folder>/Infogix/igx-data/<myConfigName>/<product>/config

Modify the following properties:


USE_EMBEDDED_HTTP_INVOKE_SERVER=true
SERVER_HOST_NAME= the host name of the cluster member
SERVER_PORT= the HTTP port number for the cluster member
SUPPORT_SSL=true
SSSL_SERVER_PORT=the HTTPS port number for the application server

Repeat step 1 and step 2 for each product.

Navigate to the httpinvoker.properties file:


<install_folder>/Infogix/igx-data/<myConfigName>/<product>/config

Change the FOLLOW_HTTP_INVOKER_REDIRECTS property to true.
Do one of the following tasks to enable this property for all nodes in the cluster.
1. Add this property to the override.properties file. See “Create the override.properties File”.
2. Move the httpinvoker.properties file to the directory defined by the CONFIG_OVERRIDE property. See “Configure the CONFIG_OVERRIDE Property”.
Run the update-config script to update your settings.

WildFly clustered deployment

To set up a clustered environment on WildFly 26.1.2, follow the instructions below. These instructions use the terms node1 and node2 to indicate the host machine for each cluster member. This procedure pertains to Windows, UNIX, or Linux.

Important: These instructions assume that you have a shared file system that is accessible from both nodes using the exact path name.

Access the shared file system. For example:
```
/net/InfogixShare/
```
Within the shared location, create a subfolder called igx, for example:
```
/net/InfogixShare/igx
```
The above installation folder, /net/InfogixShare/igx, is called <install_folder> throughout the rest of this section.
Follow the instructions to extract the installation files into the subfolder that you just created. See “Download Installation Files”.
Run the init-config script, and select the clustered servers option. See “Create Properties Files”.
Update the properties files, and validate the values in the properties file.

Configure the following properties in the appserver.advanced.properties file. Refer to the Properties Guide.


WILDFLY.1.HOME=${WILDFLY_HOME}
WILDFLY.1.HOST
WILDFLY.1.PORT_OFFSET
WILDFLY.2.HOME=${WILDFLY_HOME}2
WILDFLY.2.HOST
WILDFLY.2.PORT_OFFSET

Note: WildFly 26.1.2 uses port offset value (WILDFLY.1.PORT_OFFSET) to choose a set of known ports.

Note: For more information, see the “Application Server Properties” chapter in the Properties Guide.

The table that follows shows the HTTP and HTTPS settings for each port set.

WildFly PORT_OFFSET	HTTP Setting	HTTPS Setting
0	8080	8443
100	8180	8543
200	8280	8643
300	8380	8743
400	8480	8843
500	8580	8943

Log in to the host for node1.
From <install_folder>/Infogix/bin folder, run config-wildfly script to create the WildFly instance.
For Windows:
```
config-wildfly.bat -c <myConfigName>
```
For UNIX or Linux:
```
./config-wildfly.sh -c <myConfigName>
```
where <myConfigName> is the name of your configuration.
From the <install_folder>/Infogix/bin, execute the following command to add an administrative user to the WildFly Management realm:
For Windows:
```
add-wildfly-user.bat -c <myConfigName>
<WILDFLY_ADMIN_USER> <WILDFLY_ADMIN_PASSWORD>    
```
For UNIX or Linux:
```
./add-wildfly-user.sh -c <myConfigName>
<WILDFLY_ADMIN_USER> <WILDFLY_ADMIN_PASSWORD>        
```
where the user ID and password specified above are the same as the values provided for WILDFLY_ADMIN_USER and WILDFLY_ADMIN_PASSWORD properties in the appserver.properties file.

Note: WildFly has a separate security realm for the administrator that can log in to the console. This is different from JBoss 6.1.0 where the administrator was the SECURITY_USER.
From the <install_folder>/Infogix/wildfly/bin, execute the following command to start the WildFly instance created by config-wildfly script:

for Windows

start<myConfigName>.bat

for UNIX or Linux

start<myConfigName>.sh

where <myConfigName> is the name of your configuration. For example:

startigx.bat (.sh)

where igx is the name of the configuration if you used the default configuration. Or,

startIA.bat (.sh)

where IA is the name of your configuration.
Log in to the host for node2.
From the <install_folder>/Infogix/wildfly2/bin on node2, execute the following command to start the WildFly instance created by config-wildfly script above.
For Windows:
```
start<myConfigName>.bat
```
For UNIX or Linux:
```
start<myConfigName>.sh
```
where <myConfigName> is the name of your configuration. For example:
```
startigx.bat (.sh)
```
where igx is the name of the configuration if you used the default configuration. Or,
```
startIA.bat (.sh)
```
where IA is the name of your configuration.
Log in to the host for node1.
From <install_folder>/Infogix/bin, execute the deploy script to deploy the product.
For Windows:
```
deploy.bat -c <myConfigName> <product>
```
For UNIX or Linux:
```
./deploy.sh -c <myConfigName> <product>
```
where <myConfigName> is the name of your configuration, and <product> is the parameter for your application:
- For Assure DQ, specify IA.
- For ER, specify ER.
- For Insight, specify II.
- For Perceive, specify IV.
Important: Product parameters are case-sensitive.
Open <install_folder>/Infogix/logs/<myConfigName>/<product> and review deploy.log to verify that there were no errors.

To complete the post-deployment tasks for your application, proceed to “Post-deployment Tasks.”

“Advanced Deployment” and “Product Integration” provide instructions for advanced deployment scenarios and product integration. Refer to these chapters, as applicable.

Clustered deployments - assure_dq - 10.1.0

Assure DQ Server Installation

Requirements for a clustered deployment

Enable HTTPS requests between products

WildFly clustered deployment