Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Informatica ActiveVOS 9.2.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Apache Tomcat
  3. WebLogic
  4. IBM Websphere
  5. JBoss
  6. SameSite attribute in cookies

Server Installation, Configuration, and Deployment

Server Installation, Configuration, and Deployment

Back Next

Configuration

Configuration

This section leads you through configuration of the resources required for Process Server. You must configure your database, Apache Tomcat Server and Process Server before deploying and running Process Server. The sections below provide information for completing the configuration.

Configuring a JDBC Data Source

To configure a JDBC Datasource within WebSphere, perform the following steps
  1. Navigate to JDBC Providers under Resources.
  2. Select Create a New Database Provider.
  3. Select either a known database provider type (e.g., DB2 Universal JDBC Driver Provider) or create a new user defined provider (i.e., User-defined JDBC Provider). The table below provides information on the parameters that must be filled in.
    Parameter
    Description
    Name
    User defined or the value from the drop-down list
    Description
    User defined.
    Classpath
    The classpath for the jar(s) that contain the JDBC Driver, for example:
    • ${DB2_JDBC_DRIVER_PATH}/db2jcc.jar
    • ${DB2_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar
    Implementation Classname
    The implementation name for the data source; for example:
    • DB2= com.ibm.db2.jcc.DB2ConnectionPoolDataSource
    • mySQL = com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource
  4. Apply changes.
  5. Select the Data Sources link under Additional Properties.
  6. Create a new data source. The table below describes the properties and associated values:
    Propety
    Description
    Name
    Process Server data source
    JNDI Name
    jdbc/ActiveVOS
    Data storage helper classname (for DB2 only)
    com.ibm.websphere.rsadapter.GenericDataStoreHelperClasspath
  7. Apply changes
  8. Select Additional Properties then Connection Pool.
  9. Set the Min Connections and the Max Connections. The suggested values are min = 10 and max = 50.
  10. Select the link J2EE Connector Architecture (J2C) authentication data entries from the DataSource definition page.
  11. Create a database authorization alias to be used during EAR deployment. You should use ActiveVOSDBAlias as the name of the alias.
  12. Provide the user name and password to access the database.
  13. Press OK to return to the Data Source configuration page.
  14. Select Additional Properties then Connection Pool.
  15. Select Custom Properties and add/modify the property values as required. The table below provides examples of the properties and associated values for DB2 and MySQL:
    Property
    DB2 Value
    MySQL Value
    databaseName
    ABPEL
    ActiveVOS
    serverName
    host name where DB2 installed
    host name where MySQL installed
    portNumber
    50000
    3306
    user
    db user name
    db user name
    password
    db password
    db password
    useUnicode
    N/A
    true
    characterEncoding
    N/A
    UTF-8
    characterSetResults
    N/A
    utf8
  16. Save the changes.
  17. Test the newly created connection.
  18. Provide the user name and password to access the database.

Configuration Instructions

Before running the Configuration utility, perform the following pre-configuration steps:
  • Create a database (or tablespace) where Process Server persistence information will be stored
  • Create a default user with administrative rights to the computer and database for use by Process Server
  • Configure a JDBC Data source as described above.

First Time or New Install

If you are performing a clean installation, that is, a first-time install or a new database, you can use the Configuration utility to automatically install the database schema.

Manual Install or Update of Database Schema

It is strongly recommended that you automatically install the database schema; however, you can manually install it. Customers migrating from an earlier version should follow the instructions below.
Migrating from ActiveVOS to Process Server
If you are migrating from an earlier release of ActiveVOS, perform the following steps:
  • Manually update the Process Server database schema using the DDL patches provided in
    {install_dir}/server/tomcat_config/ddls/updates
  • Run the Configuration utility
  • Review the Release Notes for late breaking migration information
  • Review the Process Developer help topic, Migrating from Earlier Versions
Process Server can be configured to use an RDBMS database.
Relational Database Schemas
These instructions are generalized to make sure they can be followed for each database. When creating the database schema for Process Server, you can either create a new database definition or upgrade an existing definition.
  • Refer to the install a new database schema section for a new installation.
  • Refer to upgrade a database schema when performing a version upgrade.
Install a new database schema
  1. Identify your DDL. Use the information provided in the table below to locate the correct DDL file.
    Database Server
    DDL File Name and Location
    Notes
    MYSQL
    {install_dir}/server/websphere_config/ddls/ActiveBPEL_Enterprise-MYSQL.SQL
    The default database name, ActiveVOS is defined within the DDL file. If you edit this name, ensure that you do not replace ActiveVOS Enterprise, a name that is inserted into the
    AeMetaInfo
     table.
    MS SQL SERVER
    {install_dir}/server /websphere_config/ddls/ActiveBPEL_Enterprise-MYSQL.SQL
    The default database name, ActiveVOS is defined within the DDL file. If you edit this name, ensure that you do not replace ActiveVOS Enterprise, a name that is inserted into the
    AeMetaInfo
     table.
    ORACLE
    {install_dir}/server/ websphere_config/ddls/ ActiveBPEL_Enterprise- ORACLE.SQL
    Create a tablespace prior to running the DDL.
    DB2
    {install_dir}/server/ websphere_config/ddls/ ActiveBPEL_Enterprise- DB2.SQL
  2. Copy the DDL file from above, and rename it.
    Note:
     The original files must remain unchanged for the Configuration utility to work properly
  3. (Optional) Modify the database name. Be sure to see the notes above.
  4. Execute the DDL script.
  5. Permissions must be set for Process Server to access your schema. For example,
    GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE
    If Process Server does not have the permissions it needs, you will see an error message that begins as follows: Failed to get version info from the AeMetaInfo table.
Each database server provides its own mechanism or utility for executing a DDL script file. Execute the DDL script file using the appropriate utility. For example, if you are using Oracle, the utility to execute the DDL script file would be SQL Plus.
Upgrade an Existing Database Schema
To upgrade your existing Process Server database to be compatible with the new version of software, follow the instructions below:
  1. Shutdown Process Server before executing a database upgrade.
  2. Make a backup copy of your database.
  3. Identify your current running version of Process Server. Database upgrades are provided to upgrade from one version back at a time. This means that more than one upgrade script may need to be applied to your database. For example, if you are running ActiveVOS version 8.0.x, you must go to the
    updates
     folder, and apply all patch scripts with higher numbers, starting with
    [database name]-Patch-9.0.sql
    . Be sure to run the patch scripts in
    ascending
     order. Do not run any upgrade script with a version number equal to or less than your current running version.
  4. For each upgrade that needs to be applied perform the following:
    1. Identify your DDL. Use the information provided in the table below to locate the correct DDL file. Note: The updates must be applied in ascending order.
      MYSQL
      {install_dir}/server/websphere_config/ddls/updates/enterprise/ActiveBPEL_Enterprise-MYSQL-PATCH-{patch number}.SQL
      MS SQL SERVER
      {install_dir}/server/wwebsphere_config/ddls/updates/enterprise/ActiveBPEL-Enterprise-SQLSERVER-PATCH-{patch number}.SQL
      ORACLE
      {install_dir}/server/websphere_config/ddls/updates/enterprise/ActiveBPEL-Enterprise-ORACLE-PATCH-{patch number}.SQL
      DB2
      {install_dir}/server/websphere_config/ddls/updates/enterprise/ActiveBPEL-Enterprise-DB2-PATCH-{patch number}.SQL
    2. Execute the DDL script.
      Each database server provides its own mechanism or utility for executing a DDL script file. Execute the DDL upgrade script file using the appropriate utility. For example, if you are using Oracle, the utility to execute the DDL script file would be SQL Plus.

Multisite Configuration

For details, see
Process Server MultiSite Configuration
.

Security Configuration

You can find details on configuring Process Server security roles in Process Developer Help or in the Infocenter.

Configuration for Headless Mode

Process Server relies on GUI components from the Java's SWT package, such as Fonts. If you are running on a headless server (i.e., the server does not have a graphic subsystem), you may see one of the following errors in the stack trace:
  • java.lang.NoClassDefFoundError: sun/awt/X11GraphicsEnvironment
  • Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable
  • org.eclipse.birt.report.service.api.ReportServiceException
Use one of the following techniques to correct errors:
  • Configure the JVM system property
    java.awt.headless=true
     and at the command line, start the JVM with the argument:
    -Djava.awt.headless=true
  • Run a X-windows virtual frame buffer (Xvfb)

Configuration for Process Central when Using MultiTenant Feature

There an issue with WebSphere that prevents Process Central from working properly in a multi-tenant environment. There is a simple fix, however. In order to get Websphere 6.1 and 7.0 to handle servlet filters properly, you need to set the following web container property: 
com.ibm.ws.webcontainer.invokefilterscompatibility = true
See http://www-01.ibm.com/support/docview.wss?rss=180&uid=swg21284395 for general instructions on how to set web container properties

Using the Configuration Utility

The Configuration utility walks through the steps required to provide the property values for Process Server and selected resources.
Note:
Before running the utility, ensure that your server container is stopped.
Starting the Configuration Utility
Execute one of the following utilities based on your operating system:
Windows
{install_dir}/server/websphere_config/bin/config_deploy.bat
Linux
{install_dir}/server/websphere_config/bin/config_deploy.sh
If You Have Manually Installed or Updated the Database Schema
If you have manually installed or updated the database schema, when prompted, you must not select the "Install Database Schema" checkbox.
Running the Configuration Utility in Different Modes
The Configuration utility can be run with a graphical interface (default), in console mode or silently. When you run the utility your configuration options are automatically written to the install.properties file and they will be used as the defaults the next time the application is configured. One of the following parameters is accepted by the Configuration utility:
  • Help:
    help
    . This option displays the usage for console and silent modes.
  • Console mode:
    console
    . Runs the Configuration utility in text mode within a command window.
  • Silent mode:
    silent
    . Runs in the background requiring no user interaction. This option requires that you have already run the Configuration utility in default mode, which sets configuration options in the install.properties file.
An example of running the Configuration utility from the command line is:
config_deploy help
Configuration Help
The Configuration utility contains online help for each panel of the utility. Access Help by clicking the Help button on each panel. Additionally you can access the help from
{install_dir}/server/tomcat_config/doc/html/config
.

Configuring a JMS Messaging Service

You can configure a JMS Messaging Service in ActiveVOS in order to communicate with external clients and services over JMS. To set up a listener on a JMS queue or topic, you must deploy a message-driven bean
For details, refer to the JMS Messaging Service help topic from the Help link in the Process Console
0 COMMENTS
We’d like to hear from you!