Deploy on WebSphere Liberty - assure_dq - 10.1.0

Assure DQ Server Installation
Product type
Software
Portfolio
Verify
Product family
Assure
Product
Assure DQ
Version
10.1.0
ft:locale
en-US
Product name
Assure DQ, ER, Insight and Perceive
ft:title
Assure DQ Server Installation
Copyright
2025
First publish date
2005
ft:lastEdition
2025-11-28
ft:lastPublication
2025-11-28T07:35:54.959000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Infogix
L4_Investment_Segment
Legacy Infogix DQ
L5_Product_Group
Legacy Infogix DQ
L6_Product_Name
Product Feature
Assure DQ

To begin, download the WebSphere Liberty installer package from IBM's official support page:

IBM Website for WebSphere Liberty for Developers

For Windows: WebSphere Liberty Jakarta EE 8, Network Deployment Version 25.0.0.11

For Linux or Unix: WebSphere Liberty Network Deployment wlp-nd-all-25.0.0.11.jar

To install WebSphere Liberty, unzip the downloaded installer package.

Server configuration

To create and manage a new server:

  1. Open a Command-Line Interface (CLI) and navigate to the wlp/bin directory.
  2. Create a new server named server1 by executing the following command:
    • For Windows OS: server create server1
    • For Linux or Unix: ./server create server1

    This will create a server named server1 in the wlp/usr/servers directory.

  3. Start the server by executing the following command:
    • For Windows OS: server start server1
    • For Linux or Unix: ./server start server1
  4. To stop the server, execute the following command:
    • For Windows OS: server stop server1
    • For Linux or Unix: ./server stop server1
Tip: To delete a server, first stop the server, then manually delete the server folder. WebSphere Liberty does not provide a delete command.

Key locations for server files

  • Server Log: Located in the logs folder within the created server directory. It is named as messages.log.
  • server.xml: Contains all the configurations required for application installation.
  • bootstrap.properties: Holds property values to be used in server.xml and other server-level configurations, such as formatting server logs and enabling trace logging.

Liberty feature installation

The Liberty server does not come pre-packaged with features for installation. Instead, each feature required by an application must be added to the server.xml file and installed before it can be used.

To install individual features, execute the following command:

  • For Windows OS: installUtility install <featureName>
  • For Linux or Unix: ./installUtility install <featureName>

    For example:

    installUtility install jdbc-4.1

To install all features specified in server.xml at once, execute the following command:

  • In Windows OS: installUtility install <serverName>
  • In Linux or Unix: ./installUtility install <serverName>

For example:

installUtility install server1
Tip: This is a one-time operation per WebSphere Liberty installation. There is no need to repeat this step for new servers unless new features are added to server.xml.

Application deployment on WebSphere Liberty

  1. Extract the downloaded build product builds. Run the following script to extract the files to the installation folder:
    • For Windows: infogixextract.bat
    • For UNIX or Linux: ./infogixextract.sh
  2. Execute Init-config and choose option 2 (websphereLiberty) for appserver.
  3. If required, create a new SQL/Oracle Server database to verify the populate-db command. Skip this step if the database is already created and populated.
  4. Manually configure the installer properties (located in Infogix/config).
    • Update the appserver and appserver.advance files with the necessary changes such as port, host, liberty home, and other required settings.
  5. Execute the clean command.
  6. Execute Validate-config-values.
  7. Optionally, execute populate-db.
  8. Execute deploy.
  9. Execute config-websphere-liberty with the product name as an argument.

    For example:

    config-websphere-liberty.bat IA
  10. Start the server and review the server log to confirm successful deployment.
  11. Launch the application.

The config-websphere-liberty command will create these items:

  • server.xml (Product specific server.xml will replace default server.xml)
  • bootstrap.properties
  • jvm.options
  • Configuration folder which will hold the application specific configuration like IA_Server.xml
Important: If Assure and Insight are deployed together on the same JVM, or if Assure is deployed alongside Perceive on a single JVM, you will need to make additional modifications to the configuration files after executing the config-websphere-liberty command, as shown below.

Default configuration (IA_Server.xml):


<httpSession cookieName="AssureJSESSIONID" cookiePath="/infogixassure" invalidateOnUnauthorizedSessionRequestException="true"/>
<webAppSecurity includePathInWASReqURL="true" ssoCookieName="AssureLTPATOKEN"/>

Modified value (IA_Server):


<httpSession cookieName="AssureJSESSIONID" invalidateOnUnauthorizedSessionRequestException="true"/>

Default configuration (II_Server.xml):


<httpSession cookieName="InsightJSESSIONID" cookiePath="/infogixinsight" invalidateOnUnauthorizedSessionRequestException="true"/>
<webAppSecurity includePathInWASReqURL="true" ssoCookieName="InsightLTPATOKEN"/>

Modified value (II_Server):


<httpSession cookieName="InsightJSESSIONID" invalidateOnUnauthorizedSessionRequestException="true"/>