Deploying Asset Picker

Prerequisites

  • Ensure that JRE 1.8 or higher works for Asset Picker.
    Note: Asset Picker does not support clustered environment.
  • UnicaPlatformDS JNDI resource for Platform database is required for Asset Picker. See this guide to learn how to set up UnicaPlatformDS data source.
  • Ensure the DB2 database page size is increased to 16 KB before executing the Platform Installer for Unicode.

Setting Asset Picker home JVM argument

  1. Add the following JVM argument to the application server, where Asset Picker is required to be deployed.

    -DASSET_PICKER_HOME= path_where_asset_picker_is_installed

    For example: ASSET_PICKER_HOME =/opt/Platform/AssetPicker

    Point ASSET_PICKER_HOME to the directory, where Asset Picker is installed. It is installed within AssetPicker directory under UNICA_PLATFORM_HOME.

  2. Provide write permissions to the logs directory already created inside ASSET_PICKER_HOME.

Guidelines for deploying Asset Picker on JBOSS

You must follow a set of guidelines when you deploy Asset Picker on JBoss. Ensure that the version of JBoss meets the requirements that are described in the Recommended Software Environments and Minimum System Requirements document. Use the following guidelines when you deploy Asset Picker on JBoss:

Use the following guidelines when you deploy the Asset Picker product on any supported version of JBoss:
  1. Deploy the asset-viewer.war file as an enterprise application. See https://docs.jboss.org/jbossweb/3.0.x/deployer-howto.html for instructions on Deploying Web Server Application in JBoss.
  2. Complete the following task if your installation must support non-ASCII characters, for example for Portuguese or for locales that require multi-byte characters.
    • Edit the following standalone.conf script in the bin directory under your JBOSS /bin directory to add to JAVA_VENDOR.
      • -Dfile.encoding=UTF-8
      • -Dclient.encoding.override=UTF-8
      • -Djboss.as.management.blocking.timeout=3600
  3. Restart JBOSS server.

Guidelines for deploying Asset Picker on Apache Tomcat®

You must follow a set of guidelines when you deploy Asset Picker on Apache Tomcat. Ensure that the version of Apache Tomcat meets the requirements that are described in the Recommended Software Environments and Minimum System Requirements document. Use the following guidelines when you deploy Asset Picker on Apache Tomcat.
  1. Deploy the HCL asset-viewer.war file as an enterprise application on Tomcat Apache server. Complete the following tasks if your installation must support non-ASCII characters, for example for Portuguese or for locales that require multi-byte characters.
    1. Edit the setenv.sh file for the respective product instances script in the bin directory under your tomcat instances directory to add -Dfile.encoding=UTF-8 Dclient.encoding.override=UTF-8 to JAVA_VENDOR.
    2. Restart Tomcat.
  2. If deploying in a production environment, you can add JVM heap setting for that Tomcat instance in app-one/bin/setenv.sh file respectively for all the instances.

Asset Picker | User Role Creation

The procedure included in this section is not required for the following scenarios:
  • It is a fresh installation. The installation process creates this role under default partition (partition1).
  • It is an upgrade and only one partition exists in the current system.

In case, it is an upgrade and system contains more than one partition, you must execute the following command manually for each partition, except partition1. The command exists under <PLATFORM_HOME>\tools\bin directory inside your Platform installation directory. This creates Asset Picker User role under each partition.

On Windows

populateDb.bat -n AssetPicker -p <partition_name>

On Unix

populateDb.sh -n AssetPicker -p <partition_name>