Welcome
Installation Guides
Installation Guide
An installation of HCL Unica products is complete when you install, configure, and deploy the HCL Unica products . The Installation Guide provides detailed information about installing, configuring, and deploying the products.
Deploying Plan
There are general guidelines for deploying Unica Plan on WebSphere® and WebLogic.
Deploying on JBoss
You must follow a set of guidelines when you deploy Unica Plan on JBoss.

Unica Plan
Release Notes
System Requirements
Installation Guides
- Installation Guide
  An installation of HCL Unica products is complete when you install, configure, and deploy the HCL Unica products . The Installation Guide provides detailed information about installing, configuring, and deploying the products.
  - Installation overview
    An installation of HCL Unica products is complete when you install, configure, and deploy the HCL Unica products . The Installation Guide provides detailed information about installing, configuring, and deploying the products.
  - Planning the Unica Plan installation
    When you plan your Unica Plan installation, ensure that you have set up your system correctly, and that you have configured your environment to deal with any failures.
  - Preparing the data sources for Plan
    You can use the Unica Plan worksheet to enter the information that is required when you install Unica Plan.
  - Installing Unica Plan
    You must run the Unica installer to start the installation of Plan. The Unica installer starts the product installer during the installation process. Make sure that the Unica installer and the product installer are saved at the same location.
  - Configuring Plan before deployment
    Complete the configuration tasks before you deploy the web application.
  - Deploying Plan
    There are general guidelines for deploying Unica Plan on WebSphere® and WebLogic.
    - Configuration of JVM parameters for Unica products
      You must configure the following JVM parameters in the Unica porducts.
    - Deploying Plan on Websphere
      You can deploy the Unica Plan application from a WAR file or an EAR file on the WebSphere® Application Server (WAS).
    - Deploying Plan on WebLogic
      Use the following guidelines for deploying Unica Plan on WebLogic.
    - Deploying on JBoss
      You must follow a set of guidelines when you deploy Unica Plan on JBoss.
    - Deploying Plan on Tomcat
      You must follow a set of guidelines when you deploy Unica Plan on Apache Tomcat.
  - Configuring Plan after deployment
    After you deploy and start the Unica Plan application, log in and verify the installation. There are some basic configuration steps such as configuring the system user and a test user, setting up email and markup.
  - Installing reports
    Unica Plan supports integration with both IBM Cognos and Unica Insights.
  - Installing Plan in a cluster
    You can install Plan in a cluster by completing additional tasks while installing Plan.
  - Uninstalling Unica Plan
    Run the Unica Plan uninstaller to uninstall Unica Plan. When you run the uninstaller, the files that were created during the installation process are removed. For example, files such as configuration files, installer registry information, and user data are removed from the computer.
  - The configTool utility
    The properties and values on the Configuration page are stored in the Unica Platform system tables. You can use the configTool utility to import and export configuration settings to and from the system tables.
  - Unica Plan configuration properties
    The Unica Plan configuration properties on available on the Settings > Configuration page. For more details on the configuration properties, see the Plan Administrator Guide.
Upgrade Guide
Administrator Guide
With Unica Plan, you organize the people, tasks, and budget for marketing programs, while you reduce costs and time to market.
User Guide
With Unica Plan, you organize the people, tasks, and budget for marketing programs, while you reduce costs and time to market.
Integration Module
Unica Plan Integration Services combines the Unica Plan Integration Webservice, SOAP API procedures, and triggers to extend business capabilities.
API Guides
Integration Guide
Plan Offers Migration Guide
Reports
Licensing Guide
GDPR Guide
PDFs
Glossary
Notices

Deploying Unica Plan on JBoss

You must follow a set of guidelines when you deploy Unica Plan on JBoss.

Perform the following steps:
- Clear the recent items for all the users. Note: Administrator: Please communicate to all the users to clear their respective recent items prior to the migration to JBOSS.
- Clear the directory <Plan_home>/recentdata.
- Migrate to JBOSS.

From the bin directory under your JBoss installation directory, locate and open the standalone.conf or standalone.conf.bat script appropriate for your operating system in a text editor. Scroll to the JAVA_OPTIONS property, and add the following entries. Use a space to separate entries.

-Dplan.home=<Plan_Home>

Where <HCL_Unica_Home> is the path to the top-level directory and <Plan_Home> is the path to the directory where you installed Unica Plan. Typically this directory is HCL_Unica/Plan.
-Dfile.encoding=UTF-8

Make sure that the version of JBoss meets the requirements that are described in the Unica Enterprise Products Recommended Software Environments and Minimum System Requirements document. Use the following guidelines when you deploy Unica Plan on JBoss:

Use the following guidelines when you deploy the Unica Plan products on any supported version of JBoss:

Deploy the HCL plan.war file as an enterprise application.
For example: deploy <Plan_home>\plan.war
See https://docs.jboss.org/jbossweb/3.0.x/deployer-howto.html for instructions on Deploying Web Server Application in JBoss.
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 standalone.conf script in the bin directory under your JBOSS /bin directory to add -Dfile.encoding=UTF-8 -Dclient.encoding.override=UTF-8 to JAVA_VENDOR.
2. Restart JBoss server.

By default JBOSS is configured to process requests with a maximum size of 10 MB. If you expect users to download large files, configure the max-post-size as needed.

To increase the value of this parameter, directly edit the standalone configuration or domain configuration as follows:

 <buffer-cache name="default"/>
            <server name="default-server">
                <http-listener name="default" socket-binding="http" redirect-socket="https" max-post-size="20971520" enable-http2="true"/>

For more information, see JBOSS documentation.