CHORDIANT TOOLS PLATFORM

Z/OS® INSTALLATION AND CONFIGURATION GUIDE

- RELEASE 6.5
Impor t ant Notice
Chordiant, the Chordiant logo, Customer Experience, Cx, and Chordiant Mesh® are
trademarks of Chordiant Software, Inc. Wo rl d Hea dq ua r t ers
Chordiant Software, Inc.
Copyright © 1996-2010 by Chordiant Software, Inc. All rights reserved. 20400 Stevens Creek Blvd.
Cupertino, CA 95014
This document is Chordiant Confidential Information intended for the exclusive use of 1-408-517-6100
Chordiant Software, Inc., its affiliates, and its customers and partners. No part of this Fax: 1-408-517-0270
publication may be reproduced, revised, stored in a retrieval system, or transmitted, in www.chordiant.com
any form or by any means, mechanical, electronic, photocopying, recording, or
otherwise, without prior written permission of Chordiant Software, Inc. No licenses,
express or implied, are granted with respect to any of the technology described in this
document.
European Headquar te rs
Tradema rk Ack nowledgments Chordiant Software Int’l, Ltd.
BEA and WebLogic are trademarks of BEA Systems, Inc. IBM and WebSphere are Building 10, Chiswick Park
trademarks of IBM Corporation. Oracle is a trademark of Oracle Corporation. 566 Chiswick High Road
London W4 5XS, United Kingdom
All other company or product names may be trademarks or registered trademarks of +44 (0) 20 8987 3800
the respective companies with which they are associated. Fax: +44 (0) 20 8987 3902

z/OS® is a registered trademark of IBM Corporation.

P u bli s h i ng I nfo r m a t i o n
Chordiant Tools Platform Installation and Configuration Guide: Custom er Suppor t
z/OS® and WebSphere Application Server support@chordiant.com

Release 6.5 Document version 1.0 April 2010 Americas:

1-408-517-6200
Please e-mail suggestions and corrections to tech_comm_ww@chordiant.com. Toll-free: 1-877-866-7243

EMEA:
+44 (0) 20 8580 0400
Contents

Preface ....................................................................................................................................................... v

Chapter 1 Introduction ................................................................................................................................. 1

Chordiant Tools Platform ....................................................................................................................... 3
Chordiant Mesh® ..................................................................................................................................... 4
Documentation and Help ....................................................................................................................... 4

Chapter 2 Preparing the Development Environment ............................................................................. 5

Development Environment Setup ......................................................................................................... 5

Chapter 3 Preparing a Production Environment on z/OS® .................................................................. 6

Configuring Third-Party Applications ................................................................................................. 6
Database Setup ......................................................................................................................................... 6
Configuring DB2 Connect ........................................................................................................... 7
Assumptions: ........................................................................................................................ 7
Database Creation......................................................................................................................... 8
Installing LDAP ........................................................................................................................................ 9
Application Server setup ...................................................................................................................... 10
Run the Application Server Scripts on z/OS®....................................................................... 10
Configure Type 4 JDBC Connection ................................................................................................... 10
Environment Variable ................................................................................................................ 11
Configuring JDBC Provider ...................................................................................................... 11
Creating the EAR File ............................................................................................................................ 12
Deploying the EAR file ......................................................................................................................... 12
Workload Management ........................................................................................................................ 12
Installing Chordiant Decision Management (CDM) with Foundation Server ............................. 13

Appendix A Required Information Checklist .............................................................................................. 14

Application Server ...................................................................................................................... 14
Database ....................................................................................................................................... 15
LDAP ............................................................................................................................................ 16
JMS Server.................................................................................................................................... 17
JDK (Development only) ........................................................................................................... 17

Appendix B Troubleshooting ......................................................................................................................... 18

WebSphere .............................................................................................................................................. 18
Database .................................................................................................................................................. 19

Appendix C Type 4 vs Type 2 JDBC Driver Recommendation ................................................................. 21

Type 4 JDBC Driver .................................................................................................................... 21

iii
 Type 2 JDBC Driver .................................................................................................................... 21

Appendix D Configure Multiple Server Instance for Foundation Server................................................ 22

Configure Multiple Server Instance .................................................................................................... 22
Reference Documents ........................................................................................................ 23
Port Sharing ................................................................................................................................. 24

iv
Preface

The Chordiant Tools Platform Installation and Configuration Guide provides information and
procedures to install and setup Chordiant development and production environments on z/OS®
platform. This information includes installing and configuring third-party applications required
to run Chordiant, steps to verify your installation, and troubleshooting tips.

Topics covered in this section include:

• “Who Should Use this Guide”
• “Manual Organization”
• “Additional Documentation”
• “Typographical Conventions”

Who Should Use this Guide

This manual is intended for professionals responsible for installing and configuring Chordiant
applications on a z/OS® production environment. These individuals include database
administrators, system administrators, deployment personnel and developers.

Manual Organization
The Chordiant Tools Platform Installation and Configuration Guide is organized in the following
manner:

Chapter 1 Provides an overview of the installation and configuration process.

Chapter 2 Describes how to configure the development environment of

Chordiant.

Chapter 3 Describes how to configure the production environment of Chordiant.

Appendix A Provides a checklist and information sheet for your third-party

installation settings.

Appendix B Describes the tips for troubleshooting.

Appendix C Provides information on Type 4 and Type 2 JDBC Driver setup.

Appendix D Provides information on how to configure Multiple Server Instance for

Foundation Server.

v
 Additional Documentation
To install and configure a Chordiant Foundation Server, you should read and be familiar with the
following:
• IBM WebSphere Application Server Documentation
• DB2 Documentation
• Chordiant Applications Installation Guide for z/OS® platform for both WebSphere and DB2
documentation lines
• Chordiant Applications Deployment Guide
• Chordiant Servicing Applications Installation Guide
• Be familiar with deploying your custom Chordiant application(s)

For definitions of Chordiant terms, refer to the Chordiant Terminology Guide.

Typographical Conventions
This section explains how to interpret the font changes and notes that you see in this manual.

CONVENTION EXAMPLE

System filenames and pathnames
Document names and module names
Readme.txt is a text file that is stored on the
application server in the /etc (for UNIX) or
C:\ (for Windows NT) directory.
See the “Security” section within the Ongoing Tasks
document, or the online help from within the
Security module.

Names of code elements and small pieces of code Use the getInfo method
- or -
Onscreen text and text typed on the keyboard Type the password cmyk.

Screen element labels, including buttons and menus
- or -
Keys that you press on the keyboard
Variables that you must define based on your own
settings
Click OK. Then from the File menu, select Save.
To save the information on the page, press CTRL +
SHIFT + s.
{JAVA_HOME}/com/chordiant/jxw

vi z/OS Installation and Configuration Guide, release 6.5

 Gray boxes show code to be entered or viewed.

Note: A note shows important information that you should be sure to read. Many notes
refer to other sections for more information.

Tip: A tip gives suggestions on how you can use the application faster or more
efficiently.

Caution: A caution statement warns of steps you should take, or avoid, so you do not
damage your equipment, data, or system reliability.

Preface vii
 Chapter 1

Introduction

The Chordiant Tools Platform Installation and Configuration Guide provides the information you need
to install Chordiant Foundation Server and setup your development environment so you can
begin developing Chordiant solutions.

The development environment is to be setup in Windows XP or Windows Vista and for more
information refer to tech stack page of the Chordiant Mesh®.

1
2

3 4

6 7

Figure 1-1: Foundation Server and Tools Platform Installation Process

The general steps for installing Chordiant are:

1. Install third-party software for development.
2. Install Chordiant Tools Platform using the Update Manager.
3. Initialize the Chordiant workspace.

1
 4. Setup third-party products for the Chordiant development environment.
5. Verify the installation.
6. Install and configure Chordiant application(s) to be customized.
7. Install third-party software for production.

The Tools Platform runs under MyEclipse/RAD, an open integrated development environment,
enabling tool integration, productivity enhancement tools, and support for open technologies.

Install Third-party Software

Third-party software, such as an application server, database, and security must be successfully
installed and verified before Chordiant can be installed. Be sure to note the installation and
configuration settings for your supporting software, which you will be asked to supply when
configuring your development environment.

Install Chordiant Tools Platform

Chordiant is installed through MyEclipse/RAD Update Manager. Chordiant installs a runtime

version of Foundation Server and the Chordiant Tools Platform.

Configure the Development Environment

Refer to the MyEclipse/RAD Guide to finish the installation process. When the installation
process is finished, you must perform a few tasks before you can begin using the Chordiant Tools
Platform to develop applications or package them for deployment.

Configuration tasks include:

• Initializing your workspace. This step installs Chordiant core projects into your workspace.
These projects include a runtime version of Foundation Server.
• Configuring your third-party applications to run with your development environment. This
involves configuring, modifying, and executing setup scripts. You will need the installation
and configuration settings noted when installing your third-party applications.
• Verifying that your Chordiant installation is working by running a sample application.

Install Chordiant Application

After you have configured your development environment for Chordiant, you can install your
application, configure the development environment to run it, and begin using the Tools Platform
to extend and customize it. The Chordiant Servicing Applications Installation Guide provides general
steps to install applications and configure the development environment for them. Some
applications also provide additional, application-specific installation and deployment documents
on the installation CD.

Chapter 1: Introduction 2
Chordiant Tools Platform

C H O RD I A N T TO O L S P L A T FO R M
The Chordiant Tools Platform provides a robust development environment in which to create,
modify, and extend Chordiant applications. The Tools Platform provides:
• A Foundation Server runtime
• Source code necessary to develop applications
• Third-party software needed for runtime execution
• Tools to aid in application development

Some tools, such as the Business Process Designer, are fully integrated with the Tools Platform.
Others can optionally install to the environment, and still others operate as standalone tools
outside the Chordiant solution. You can further extend the development environment by
installing other third-party plug-ins. MyEclipse/RAD modular structure simplifies installing
features, updates, and additional plug-ins through native installers or the MyEclipse/RAD
Update Manager.

When an application is ready to be deployed, it is packaged along with supporting files,

Chordiant runtime, and configuration, into an EAR file and deployed on the production system.

All tools listed in the tech stack page on the Chordiant Mesh® or on your installation CD are either
required or recommended for performing specific solution design and implementation functions.

The following Chordiant and third-party tools can be integrated with the Chordiant Tools
Platform:
• Business Component Generator—Creates application components from any modeler. See the
Chordiant Foundation Server Application Components Developer’s Guide for information about
details on creating your model, on using the Foundation UML, and on generating your
application components.
• Business Process Designer—A fully integrated tool that lets you build workflows graphically.
Refer to the Chordiant Tools Platform Business Process Designer Developer’s Guide for more
information about creating workflows.
• Application Packaging Manager—Packages application WARs, EJBs, and other components
in a deployable EAR file. See the Chordiant Applications Deployment Guide for more information
about using the APM to package your applications for deployment.

3 z/OS Installation and Configuration Guide, release 6.5

 Chordiant Mesh®

C H O RD I A N T M E S H ®
The Chordiant Mesh® is Chordiant’s online community of developers and users. Visit the
Chordiant Mesh®, located at https://www.chordiant.net to:
• Download daily builds or milestone releases
• Participate in online discussions about new or existing features
• Learn about new features being developed
• Participate in new feature development
• Read documentation
• Log a bug
• Fix a bug
• Find out how you can participate

Go to the Chordiant Mesh® site to learn more about how you can be part of the solution.

DOCUMENTATION AND HELP

Before you begin the installation process, be sure that you have reviewed this guide and
understand its contents. If you have any questions, contact Chordiant Customer Support or your
customization expert. Chordiant provides documentation and help from a number of sources:
• Chordiant documentation is installed when you install the Chordiant Tools Platform. To
access help files in MyEclipse/RAD, select Help | Help Contents. You should see a link to
Chordiant Documentation in the Help table of contents.
• View and print Chordiant documentation on the Chordiant Mesh®.
• The Chordiant Documentation List provides a quick reference for finding the appropriate
Chordiant document by the task or customization point you are working on, such as creating
business services or deploying an application.
• Search across Chordiant PDFs. For instructions, refer to the Chordiant Documentation List.

Chapter 1: Introduction 4
 Chapter 2
Preparing the Development
Environment

This chapter describes preparation tasks required to setup a development environment for
running Chordiant Applications. To do so, you must install and configure third-party applications
on your development system. These products include your application server, database, security,
and JMS. In addition, your application may require the installation of other supporting software.

D E V E L O P M E N T E NV I RO N M E N T S E T U P
The development environment of Chordiant can be configured either on WebSphere/MyEclipse
or WebSphere/RAD environment. The procedure is similar to the steps detailed in the existing
documentation set.

For installing Chordiant Tools Platform on RAD/WebSphere or MyEclipse/WebSphere,

configuring development environment and deploying ChordiantEAR project refer to:
• Chapters 2-6 in the Chordiant Tools Platform Installation and Configuration Guide - MyEclipse and
WebSphere Application Server
• Chapters 2-6 in the Chordiant Tools Platform Installation and Configuration Guide - RAD and
WebSphere Application Server

For additional information on Installation and configuration refer to the following guides:
• Chordiant Tools Platform Installation and Configuration Guide - RAD and WebSphere Application
Server
• Chordiant Tools Platform Installation and Configuration Guide - MyEclipse and WebSphere
Application Server
• Chordiant Applications Deployment Guide for WebSphere Application Server

5
 Chapter 3
Preparing a Production Environment on
z/OS®

This chapter describes configuring third-party applications in your production environment. You
need to note information about your third-party application installations. This information is
needed to configure Chordiant for production. Appendix A provides a checklist of the
information required.

Note: Deployment of Chordiant Foundation Server and any associated applications

assumes that your network topology and server layout is in accordance with IT
industry security considerations and best practices.

Be sure to read your third-party installation and setup instructions carefully. You
may need to set environment variables and download patches or fixes in order to
complete your installation successfully.

All softwares must be licensed and legally installed from the appropriate parties.

When installing third-party applications, we strongly recommend that you note your settings on
the form provided in Appendix A. You will need this information when you build your EAR file.

C O N F I G U R I N G T H I RD -P A R T Y A P P L I C A T I O N S
Before you can deploy an application to production, you must install and configure third-party
applications on your production system. These products include your application server, database
and LDAP. In addition, your application may require the installation of other supporting
software.

Note: Installation of third-party software is not covered in this document. Please refer to
the appropriate third-party documentation for installation steps.

DATABASE SETUP
This section describes creating and configuring DB2 database for z/OS® platform.

6
Database Setup

Configuring DB2 Connect

This section covers configuring DB2 Connect on a remote system (for example Windows) to access
the z/OS® Subsystem.

Assumptions:
1. z/OS® DB2 Subsystem environment is setup and made accessible by the z/OS® System
Administrator.
2. DB2 Connect Software is installed in the remote environment to connect to z/OS® subsystem.

For more information on DB2 Connect installation procedures, refer to the IBM DB2
documentation available with the software.

Steps to connect to the z/OS® Subsystem:

1. Launch DB2 Command prompt, (for example, on Windows Start | Programs | IBM DB2 |
DB2COPY | Command Line Tools | Command Window)
2. To catalog the node, run the following statement:
db2 catalog tcpip node <node_name> remote <ip_address> server <port_no> ostype OS390

Here, the <node_name> denotes the name by which the z/OS® server is identified on the local
windows machine.
For example, db2 catalog tcpip node 240cfs remote x.x.x.10 server 4019 ostype OS390
3. To catalog the z/OS® subsystem, run the following statement:
db2 catalog database <subsystem_name> as <subsystem_alias> at node <node_name> authentication server

For example, db2 catalog database cfs240db as cfs240db at node 240cfs authentication server
4. To catalog the Database Connection Services (DCS) database, run the following statement:
db2 catalog dcs database <subsystem_alias> as <subsystem_alias>

For example, db2 catalog dcs database cfs240db as cfs240db

Note: The above command stores information about remote host or System i™
databases in the Database Connection Services (DCS) directory. These databases
are accessed through an Application Requester (AR), such as DB2® Connect™.
Having a DCS directory entry with a database name matching a database name in
the system database directory invokes the specified AR to forward SQL requests
to the remote server where the database resides.

5. To connect to the Subsystem, run the following statement:

db2 connect to <subsystem_alias> user <username> using <password>

For example, db2 connect to cfs240db user pj8051 using <password>

7 z/OS Installation and Configuration Guide, release 6.5

 Database Setup

Database Creation

Note: SYSADM/DBADM credentials are required to create the database.

In the scripts the default database name is CHRD and the schema name is
CCSOWN. Modify the defaults appropriate to the environment.

Once connected to the DB2 Subsystem through DB2 Connect, execute the following steps for
creating the DB2 Foundation Server database on z/OS® machine:
1. Database creation scripts are part of the CFS_on_zOS.zip and located under {Foundation
Third Party}/Database/data/database/zOS folder. Unzip the contents from
CFS_on_zOS.zip into a staging directory in the remote environment.
2. Change to staging directory.
3. To create the Foundation Server database, run the statement:
db2 –tvf 01_create_database.ddl –z 01_create_database.out

4. To create tables in the Foundation Server database using explicit tablespaces, run the
statements mentioned below:
db2 -tvf 02_create_tablespaces.ddl -z 02_create_tablespaces.out
db2 -tvf 03_create_tables_in_tbsp.ddl -z 03_create_tables_in_tbsp.out

To create the tables using implicit tablespaces, run the statement mentioned below:
db2 –tvf 03_create_tables_default.ddl –z 03_create_tables_default.out

Note: Appropriate sizes need to be set for PRIQTY and SECQTY parameters when
tablespaces are created explicitly. Please check the DB2 for z/OS® documentation
for more details on creating tablespaces and related parameter settings.

By default, z-parm values are used and may not be sufficient for some Tables.
For example:
Create tablespace cfsflx18 in Foundation Server using stogroup sysdeflt priqty 12 erase
yes bufferpool bp8k0 segsize 16 logged locksize any close no

Refer your DB2 documentation for more details on creating tablespaces and
tablespace parameters.

5. To create Views, run the statement:

db2 –tvf 04_create_views.ddl –z 04_create_views.out

6. To create Non-Unique-Indices, run the statement:

db2 -tvf 05_create_nonunique_indices.ddl -z 05_create_nonunique_indices.out

Chapter 3: Preparing a Production Environment on z/OS® 8

Installing LDAP

7. To create Unique Indices, run the statement:

db2 -tvf 05_create_unique_indices.ddl -z 05_create_unique_indices.out

Note: Do not run the Unique Indices script for implicit tablespaces.

8. To create the Trigger, run the statement:

db2 -td# -vf 06_create_triggers.ddl -z 06_create_triggers.out

9. To create the Foreign Keys, run the statement:

db2 -tvf 07_create_fks.ddl -z 07_create_fks.out

10. To create the sequences, run the following statement:

db2 -tvf 08_create_sequences.sql -z 08_create_sequences.out

11. To insert out of the box data into tables, run the statement:
db2 -tvf 09_insert_data.sql -z 09_insert_data.out

12. Verify logs for any errors to confirm the successful creation of database.
13. Connect to the database and use the following statement to verify the installed database
components information:
db2 "select schemaversion, installtype from schemainfo”

Note: The drop scripts provided can be used to drop the database and the sequences.

I N S T A L L I N G L DA P
To install LDAP, refer to either the Chordiant Tools Platform Installation and Configuration Guide -
MyEclipse and WebSphere Application Server or the Chordiant Tools Platform Installation and
Configuration Guide - RAD and WebSphere Application Server.

Note: z/OS® does not support the SUN ONE/ Open DS LDAP Servers and therefore
LDAP needs to be installed on Windows XP SP2 or Solaris 10 environment or the
setup scripts need to be modified as appropriate for other LDAP vendors or
environments.

9 z/OS Installation and Configuration Guide, release 6.5

 Application Server setup

APPLICATION SERVER SETUP

This section describes each of the settings for configuring your application server setup.

Note: The distributed platforms (non-z/OS® platforms) are built on a single process
model. The entire server runs in one single Java Virtual Machine (JVM) process.
However, WebSphere z/OS® is built using a federation of JVMs, each executing in
a different operating system process that collectively represents a single server
instance.

Each JVM in the federation is not identical because one JVM is given preference
and holds the external endpoints of the server. This JVM is called the controller
(controller region). The other JVMs are either servants (servant regions) or adjunct
(control region adjunct process). The adjunct is a special case of a servant process.
Customer-installed applications execute only in the servant regions. The adjunct
process houses the platform messaging component.

To configure the application server setup, generate the export.zip file by referring to the
“Running Third-Party Application Setup Scripts” from Chordiant Application Deployment Guide for
WebSphere Application Server.

Run the Application Server Scripts on z/OS®

1. Upload the export.zip file to any temp location in z/OS® and unzip:
bash-2.03# unzip export.zip

2. To run the application server setup scripts execute the following command:
{WAS_Install_Root}/profiles/default/bin/ws_ant.sh -verbose -f setup.xml
>/tmp/out 2>&1

The build successful message appears. Open the log file to check for any errors.

C O N F I G U R E TY P E 4 J D B C C O N N E C T I O N
This section covers the steps to configure Type 4 JDBC connection for Chordiant applications.

Note: For JDBC driver recommendation, refer Appendix C, “Type 4 vs Type 2 JDBC
Driver Recommendation”.

Chapter 3: Preparing a Production Environment on z/OS® 10

Configure Type 4 JDBC Connection

The Type 4 JDBC driver:

• Supports JDBC 2.0 and 3.0 specification to deliver the maximum flexibility and performance
required for enterprise applications
• Delivers robust connectivity to the latest DB2 for z/OS® and WebSphere Application Server
for z/OS®
• Provides support for distributed transaction support (two-phase commit support)
• Enables custom Java applications that do not require an application server to run in a remote
partition and connect to DB2 for z/OS®

For Type 4 connection, you need to set the WebSphere environment variables and configure JDBC
provider as described in the section below.

E nv i ro n m e n t Va r i a bl e
1. Load the WebSphere admin console.
2. From the WebSphere Application Server Admin panel, select Environment |Manage
WebSphere Variables | Node Level.
3. Set the DB2UNIVERSAL_JDBC_DRIVER_PATH pointing to the directory containing JDBC
driver files.
For example, if JDBC driver is installed at /usr/lpp/jcc, set the environment variable to the
location as specified below:
DB2UNIVERSAL_JDBC_DRIVER_PATH = /usr/lpp/jcc/classes

C o n f i g u r i n g J D B C P rov i d e r
From the WebSphere Application Server Admin console, click Resources | JDBC Providers
1. Set the environment variable for ChordiantXAds and ChordiantNoXAds as below:
${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar
${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar

2. Verify that the settings for other parameters are correct and click OK.
3. To set the Custom Properties of the connection, select Resources |JDBC Providers |DB2
Universal JDBC Provider | Data Sources | Custom Properties
4. In the Custom Properties dialog box, specify the following values as shown in Figure 3-1:

11 z/OS Installation and Configuration Guide, release 6.5

 Creating the EAR File

Figure 3-1: Custom Properties Dialog Box

• DatabaseName - Set the value to the z/OS® subsystem name in which the DB2 database is
located.
• DriverType - Set the value to 4 to indicate a JDBC Type-4 connection.
• ServerName - Set the value to IP address (nn.nn.nn.nn) or the hostname
(hostname.domainname) of the DRDA server (DB2 server) system.
• PortNumber - Set the value to the port number of DRDA server (DB2 server) system.

CREATING THE EAR FILE

To generate the ChordiantEAR file refer to the steps documented under “Creating the EAR file”
described in Chordiant Applications Deployment Guide for WebSphere Application Server.

D E P L OY I N G T H E E A R F I L E
Deploy the Chordiant EAR file following standard WebSphere Application Server procedures.

WO R K L O A D M A N A G E M E N T
Workload management (WLM) is a new feature of WebSphere Application Server for z/OS®
systems. It is used to manage the performance of WebSphere applications. WLM optimizes the
distribution of incoming work requests to the application servers, enterprise beans, servlets, and
other objects that can most effectively process the requests. It also provides failover when servers
are not available, improving application availability.

For more information on Workload management feature, refer the Workload management for
z/OS®.

Refer to Appendix D, “Configure Multiple Server Instance for Foundation Server” for instructions
on how to leverage the Workload management features for Chordiant applications.

Chapter 3: Preparing a Production Environment on z/OS® 12

Installing Chordiant Decision Management (CDM) with Foundation Server

I N S T A L L I N G C H O RD I A N T D E C I S I O N M A N A G E M E N T ( C D M )
WITH FOUNDATION SERVER
To integrate CDM with Foundation Server, refer to either the Chordiant Tools Platform Installation
and Configuration Guide - MyEclipse and WebSphere Application Server or the Chordiant Tools Platform
Installation and Configuration Guide - RAD and WebSphere Application Server.

13 z/OS Installation and Configuration Guide, release 6.5

 Appendix A

Required Information Checklist

When installing and configuring supporting third-party software, record the information
described in the following tables. This information will be required when you configure your
Chordiant installation in the Tools Platform.

Application Server

REQUIREMENT DESCRIPTION VALUE (RECORD HERE)

Administration Tool socket Gateway used for the system.

gateway service connection port

J2C alias name Java 2 connection authentication

data entry used by the resource
adapters and JDBC data source.

Listen address Name of the server where

WebSphere is running.

Listen port Port number used to connect to

the Chordiant server (the default
port is 80).

Node name Name of the system where the

application server is installed.

Bootstrap port ORB bootstrap port to use if you

are connecting through RMI.

SOAP port Connector port to use if you are

connecting through SOAP.

Server name Name of the application server.

Virtual host name Logical name used to configure

web applications to a particular
host name.

VRU socket port Port that Chordiant uses to

communicate with the VRU.

Shutdown socket port Port where Foundation Server

listens for the shutdown
command.

Table A-1: Application Server Settings

14
Database

REQUIREMENT DESCRIPTION VALUE (RECORD HERE)

Database host name Physical name of the database

server in your environment.

Database name Name of the Oracle database

instance associated to the
Chordiant database, or the alias
or name of the DB2 Chordiant
database.

Database owner/password User who owns the regular

Chordiant database schema
objects. The defaults are
ccsowner/ferrari.

Database port number Port that connects to your

Chordiant database. For Oracle,
the default port is 1521. For DB2,
the default port is 5000.

Database user/password User who does not own the

regular Chordiant database
schema objects, but uses them
through Chordiant applications.
The defaults are
pduser/mappings.

Non-transactional data source JDBC connection that does not

name support transactions.

Tablespace names (dataspace For data and indexes. The

and indexspace) defaults are DEV and IDX.

Transactional data source name JDBC connection that supports

transactions.

Table A-2: Database Settings

15 z/OS Installation and Configuration Guide, release 6.5

L DA P

REQUIREMENT DESCRIPTION VALUE (RECORD HERE)

Administration Manager email Email address used by the profile

address manager to send
administration-related emails.

SMTP server name Name of the SMTP server that the

Profile Manager can use to send
emails.

Administrator password Password used to log into

Directory Server.

Location of OpenDS Directory Drive and directory where

Server installation OpenDS LDAP is installed.

Security authentication domain Base DN of the authentication

name domain.

Security authentication host Name of the server where LDAP

name is installed.

Security authentication Subtree that contains the users.

organizational unit

Security authentication port LDAP server port number.

number

User profile cache size Number of users to hold in cache.

Table A-3: LDAP Settings

Appendix A: Required Information Checklist 16

JMS Server

REQUIREMENT DESCRIPTION VALUE (RECORD HERE)

JMS J2C Alias Name Java 2 connection authentication

data entry to be created that will
be used by the resource adapters
and JDBC data source.

Service Integration Bus Name Name of the service integration

bus.

Table A-4: JMS Settings

J D K ( D ev e l o p m e n t o n ly )

REQUIREMENT DESCRIPTION VALUE (RECORD HERE)

Java runtime location Location where the Java runtime

is installed.

Table A-5: JDK Settings

17 z/OS Installation and Configuration Guide, release 6.5

 Appendix B

Troubleshooting

This appendix describes some tips for troubleshooting your installation.

WE B S P H E R E
Data source test connection from Admin console fails when
setting up
Be sure that the JDBC Provider and data sources are configured at the right scope levels.

If you configure data sources:

• With cell scope definitions, the Deployment Manager will test that connection.
• With node scope, the Nodeagent will test that connection.
• With server scope, the Server will test that connection.

Test connection fails when the JDBC provider is configured at server scope and data sources at cell
scope. Here, when the deployment manager tries to test the connection, it is unable to find the JAR
files for the driver as no JDBC provider definitions are available.

Figure B-1: Data sources test connection

18
Database

To avoid test fail, you can either:

• Define the scope of the data sources on server scope
• Define the scope of the JDBC Provider on a cell scope

Note: It is recommended that you define the JDBC Provider on a higher level.

XML Parser ex ceptions in WebS phere Application Ser ver V7

logs
WebSphere Application Server V7 throws Web.xml parsing exception due to the unavailability of
required DTDs where the application server is hosted.

To avoid these errors on the server logs follow the below steps:
1. Locate web-app_2.3.dtd under {WAS_INSTALL_ROOT}/properties/schema/j2ee
directory.
2. Create a jar such that the web-app_2.3.dtd exists in javax.servlet.resources package within the
jar file.
3. Open the WebSphere Application Server Administration console and create a shared library
pointing to the jar file created above.
4. Go to Servers | Server Types | WebSphere application servers | {Server Name} | Java and
Process Management | Class Loader.
5. Create a new class loader with classes loaded with the local class loader first (parent last)
option.
6. Select the created class loader and access Shared library references, and assign the shared
library created in Step 3.
7. Save the Configuration and re-start the server.

DATABASE
When using a DB2 for z/OS® messaging data store, the tables are not created dynamically. These
tables must be created manually before starting the messaging engine.

You can find the sibDDLGenerator.sh in the AppServer/bin directory of WebSphere. To have
separate message stores for the cluster setup for the two buses, you need to run everything twice.
Below are the commands to generate the DDL files:

./sibDDLGenerator.sh -system db2 -version 8.1 -platform zos -schema CHRDOWN -database SIBCHRD -user
CHRDOWN -statementend ';' -storagegroup SYSDEFLT >/tmp/sibDDL_CHRDOWN.txt

19 z/OS Installation and Configuration Guide, release 6.5

 Database

./sibDDLGenerator.sh -system db2 -version 8.1 -platform zos -schema CCSOWNER -database SIBCCSO -user
CCSOWNER -statementend ';' -storagegroup SYSDEFLT >/tmp/sibDDL_CCSOWNER.txt

Use the DB2 Connect to connect to DB2 and submit the DDL scripts from the command to create
the tables specific to the messaging engine.

Chapter B: 20
 Appendix C
Type 4 vs Type 2 JDBC Driver
Recommendation

This chapter provides recommendation on the JDBC driver that can be configured with
Foundation Server.

Ty p e 4 J D B C D r i v e r
Chordiant recommends the use of Type 4 JDBC driver with Foundation Server when the
Application Server and the Database Server are on different machines. The Type 4 JDBC driver
directly connects to the remote database and is much faster than the Type 2 JDBC driver.

Type 4 JDBC driver is much simpler to install and use when compared to Type 2 .

Ty p e 2 J D B C D r i v e r
It is recommended to use Type 2 JDBC driver when both the Application Server and the Database
Server are on the same machine. The Type 2 JDBC driver is optimized for this topology as it
utilizes CPU specific features such as memory sharing across processes. This reduces TCP/IP
network calls to remote databases.

In case the Application Server and the Database Server are configured with Type 2 JDBC driver on
different machines, the internal database mandates alias to be created for all remote database
tables. Due to the complexity involved with this approach, it is not recommended to configure
Type 2 driver with this configuration.

21
 Appendix D
Configure Multiple Server Instance for
Foundation Server

This chapter describes how to configure Multiple Server Instances for Foundation Server to
leverage the Workload Management feature. This feature is provided by WebSphere Application
Server for z/OS ®.

CONFIGURE MULTIPLE SERVER INSTANCE

1. From the administrative console, click Servers | Application servers | server_name.
2. Under Server Infrastructure, click Java and Process Management | Server Instance.

Figure D-1: Configure Multiple Server Instance

3. Select the Multiple Instances Enabled checkbox.

4. Specify the Minimum and Maximum Number of Instances.
5. Click Apply to finish the Server Instance changes.
6. Click OK and then click Save to save your configuration changes.

22
Configure Multiple Server Instance

Set the WLMStatefulSession property to true:

1. Click Servers > Applications servers, and then select the server.
2. Under Server Infrastructure, click Administration > Administration Services, and then,
under Additional Properties, click Custom Properties.
3. Click WLMStatefulSession and change the value in the Value field to true if it is currently set
to false.

Figure D-2: WLMStatefulSession to true

4. Click Apply and then click Save and Synchronize to update your changes.

Reference Documents
Refer to the following sections from IBM Information Centre for more information:
• For configuration and control of number of server instances, refer to the Controlling the
number of servants section.
• For enabling the multiple server instances, refer to the Enabling multiple servants on z/OS®
section.
• For configuring WLM even distribution of HTTP session objects across the multiple servant
processes, refer to the Configuring an application server to use the WLM even distribution of
HTTP requests function section.

23 z/OS Installation and Configuration Guide, release 6.5

 Configure Multiple Server Instance

Po r t S h a r i n g
Ensure that the Foundation Server ports have been shared at the profile dataset to avoid port
conflicts during server startup. This is a mandatory step for Foundation Server to work in an
environment with Multiple Server Instances.

To obtain the port values including the ChordiantVirtualHost port, go to Admin

Console|Application Servers | ChordiantAppServer | Process Definition | Servant | Java
Virtual Machine | Custom Properties as shown in Figure D-3:

Figure D-3: Custom JVM Properties

Appendix D: 24