Interactive installation guide

Select the options that apply to your environment to generate a customized installation guide for () applications.

To install the applications follow these steps:

Planning checklist

Before you install the applications, ensure to review the information in the following planning checklist.

	Planning task	More information
	Verify that your hardware and software meet the minimum system requirements. In this release of , the required Java version is 11.	System requirements
	Get the product installation media. For local repository download, you need approximately five gigabytes (5 GB) of hard drive space to download and extract your product installation media.	The server installation files can be downloaded from jazz.net
	Review your installation topology. Whether you are trying out the , or installing the solution in your production environment, click the link at the right to see and study different installation topology examples. The examples include the following: evaluation topology, departmental topology, and distributed enterprise topology.	Installation process and topology examples
	Synchronize the clocks on all machines. In a distributed environment, ensure that the clocks on all machines are synchronized using the Network Time Protocol (NTP).	For more information about NTP, visit the Network Time Protocol website
	Learn about licensing. The licensing scheme is role-based. When you purchase a role-based license, you will have read, write, and comment access to some or all of the capabilities of the applications.	Client access license management
	Learn about query and search index management. These Deployment wiki articles discuss different applications that index query information. In addition, the second part discusses administration tasks related to index management and index storage details.	Part 1: Query, search and indexing technologies in Part 2: Indices storage and management (backup, recovery and recreation)

Installation process and topology

Planning your environment is critical during the installation process, particularly if you plan to use this installation for departmental or enterprise development. See Examples: Installation process and topology to learn about different installation process and topologies.

Example topology: Two-server evaluation

To evaluate the complete () solution, at least two-server topology is required along with an enterprise database (IBM Db2 or Oracle). Use the primary node to host (), core applications, and trial license keys. Configure the second node to host the reporting applications.

Example topology: Departmental

A common installation topology is an () departmental topology with IBM WebSphere Liberty and an enterprise database management system (IBM Db2 or Oracle).

Example topology: Distributed enterprise

A common installation topology is a distributed deployment of a () enterprise topology with IBM WebSphere Liberty and an enterprise database management system, such as IBM Db2, Db2 for z/OS, or Db2 for i.

Requirements for a clustered environment

To set up a clustered environment for your applications, you need the following servers:

One server to host and ( can be installed on its own dedicated server).
Two or more nodes to host the application instances.
Two or more nodes to host the QM application instances.
One server for the load balancer (HAProxy). You can install a separate load balancer for each application, or use the same load balancer to route traffic to multiple applications.
One server for the MQTT broker ().
One server for the database.

Note: The is a Java application that by default, is installed on . To gain performance, consider adding another server in the cluster, dedicated to the .

To set up a system with HAProxy high availability, you need the following servers:

One server to host .
Two servers to host (one in standby mode).
Two or more nodes to host the application instances.
Two or more nodes to host the QM application instances.
Two servers for the load balancer (HAProxy).
Two servers for the MQTT broker ().
One server for the database.

All servers in the environment must have their fully qualified host names configured. When you update the /etc/hosts file, use the IP fully-qualified-host-name alias [,alias] format. Note that the fully qualified host name must appear before any alias. If it does not, clustering might not be enabled for multiple nodes.

For a list of system requirements, see System requirements.

Set up a clustered environment for

Set up the HAProxy load balancer

Note: The configuration directive added for SameSite needs HAProxy version 2.2 or later.

Note: Installation of HAProxy load balancer is not supported on Windows platforms.

You must install and configure HAProxy before the cluster can be activated. For more information about HAProxy, see www.haproxy.org.

Note: You can also configure and use IHS instead of HAProxy, but only one of these two methods must be used in a cluster for load balancing.

I. Installing a non-Dockerized version of HAProxy

HAProxy is part of the official Red Hat Linux repository and can be installed by using the yum command. You must have root user permissions or use the sudo command to do the installation.

To install HAProxy, open a command shell and enter the following command:
yum -y install haproxy
By default HAProxy is installed in the /usr/local/haproxy/etc/haproxy directory. Go to the HAProxy installed directory and back up the haproxy.cfg file. For example, create a haproxy.cfg.backup file.
Open the haproxy.cfg file for editing and configure it as needed. Use the following example as a reference. For more details about configuration language and available options, see the HAProxy Configuration Manual.

Note: If your is fronted by the HAProxy, see this Depolyment wiki document for the haproxy.cfg sample file.

haproxy.cfg sample file for clustering

#---------------------------------------------------------------------
# Example configuration for a possible web application. See the
# full configuration options online.
#
# http://haproxy.1wt.eu/download/1.6/doc/configuration.txt
#
#---------------------------------------------------------------------

#---------------------------------------------------------------------
# Global settings
#---------------------------------------------------------------------
global
# If not using the dockerized version,
# to have these messages end up in /var/log/haproxy.log you will
# need to:
#
# 1) configure syslog to accept network log events. This is done
# by adding the '-r' option to the SYSLOGD_OPTIONS in
# /etc/sysconfig/rsyslog
#
# 2) configure local2 events to go to the /var/log/haproxy.log
# file. A line like the following can be added to
# /etc/sysconfig/rsyslog
#
# local2.* /var/log/haproxy.log
#
# 3) uncomment the line below and comment the other log line
#log 127.0.0.1 local2
log /dev/log local2

chroot /var/lib/haproxy
pidfile /var/run/haproxy.pid
maxconn 6000
user haproxy
group haproxy
daemon

# turn on stats unix socket
stats socket /var/lib/haproxy/stats

tune.ssl.default-dh-param 2048

#---------------------------------------------------------------------
# common defaults that all the 'listen' and 'backend' sections will
# use if not designated in their block
#---------------------------------------------------------------------
defaults
mode http
option dontlognull
option http-keep-alive
option redispatch
retries 3
timeout http-request 10s
timeout queue 1m
timeout connect 10s
timeout client 2h
timeout server 2h
timeout http-keep-alive 10s
timeout check 10s
maxconn 6000

#---------------------------------------------------------------------
# main frontend which proxys to the backends
#---------------------------------------------------------------------
frontend lanneluc-proxy
bind *:80
bind *:9443 ssl crt /etc/haproxy/ssl/proxy.pem no-sslv3
log global
option httplog
mode http
capture cookie SERVERID len 32
redirect scheme https if !{ ssl_fc }
maxconn 2000 # The expected number of the users of the system.
# Limits the sockets to this number of concurrent connections. Extraneous
# connections will remain in the system's backlog until a connection is
# released. If unspecified, the limit will be the same as the frontend's
# maxconn.
default_backend ccm

backend ccm

option forwardfor
http-request set-header X-Forwarded-Port %[dst_port]
http-request add-header X-Forwarded-Proto https if { ssl_fc }
fullconn 1000 # if not specified, HAProxy will set this
# to 10% of 'maxconn' specified on the frontend

balance leastconn
cookie SERVERID insert indirect nocache secure attr "SameSite=None"

# minconn = 100, the server will always accept at least 100,
# but no more than 'maxconn' connections. Should be the same as Liberty
# settings in server.xml
# maxconn = 500, the max number of connections that will be sent to a server.
# The overage will be queued. The total for all nodes should be equal to maxxcon
# on 'frontend'
server qm1 node1.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm1 verify none
server qm2 node2.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm2 verify none
server qm3 node3.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm3 verify none
server qm4 node5.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm4 verify none

# Uncomment the following section if your MessageBroker is fronted by HAProxy (for example if in High Availability mode)
#
# # connect MessageBroker cluster in tcp mode (N servers if HA mode, or a single server if IoT MessageBroker just must be fronted by proxy)
# listen MessageBroker
# bind *:1883
# mode tcp
# balance leastconn
# option tcplog
# server MessageBroker1 [MessageBroker server 1 URI]:1883 check
# server MessageBroker2 [MessageBroker server 2 URI]:1883 check
# # connect MessageBroker cluster in HTTP mode to allow gathering of MQTT statistics (6.0.6 and newer only) (N servers if HA mode, or a single server if IoT MessageBroker just must be fronted by proxy)
# listen MessageBroker_REST
# bind *:9089 ssl crt /etc/haproxy/ssl/msigh.pem no-sslv3 # Port (9089) must match that configured in MessageBroker, and the same port needs to be specified in MQTTStatsService advanced property
# mode http
# option tcp-check # Must tell HAProxy to use TCP port to do health checks
# balance leastconn
# # Same number of entries and same servers as in the section above:
# server MessageBroker_REST1 [MessageBroker server 1 URI]:9089 check port 1883 # Same ports (1883 and 9089) as used elsewhere in this file.
# server MessageBroker_REST2 [MessageBroker server 2 URI]:9089 check port 1883 # Same ports (1883 and 9089) as used elsewhere in this file.

listen statistics
bind *:1936
stats uri /
stats admin if TRUE
stats enable
stats hide-version
stats auth root:clu8ter8
stats refresh 5s

haproxy.cfg sample file for QM clustering

#---------------------------------------------------------------------
# Example configuration for a possible web application. See the
# full configuration options online.
#
# http://haproxy.1wt.eu/download/1.6/doc/configuration.txt
#
#---------------------------------------------------------------------

#---------------------------------------------------------------------
# Global settings
#---------------------------------------------------------------------
global
# If not using the dockerized version,
# to have these messages end up in /var/log/haproxy.log you will
# need to:
#
# 1) configure syslog to accept network log events. This is done
# by adding the '-r' option to the SYSLOGD_OPTIONS in
# /etc/sysconfig/rsyslog
#
# 2) configure local2 events to go to the /var/log/haproxy.log
# file. A line like the following can be added to
# /etc/sysconfig/rsyslog
#
# local2.* /var/log/haproxy.log
#
# 3) uncomment the line below and comment the other log line
#log 127.0.0.1 local2
log /dev/log local2

chroot /var/lib/haproxy
pidfile /var/run/haproxy.pid
maxconn 6000
user haproxy
group haproxy
daemon

# turn on stats unix socket
stats socket /var/lib/haproxy/stats

tune.ssl.default-dh-param 2048

#---------------------------------------------------------------------
# common defaults that all the 'listen' and 'backend' sections will
# use if not designated in their block
#---------------------------------------------------------------------
defaults
mode http
option dontlognull
option http-keep-alive
option redispatch
retries 3
timeout http-request 10s
timeout queue 1m
timeout connect 10s
timeout client 2h
timeout server 2h
timeout http-keep-alive 10s
timeout check 10s
maxconn 6000

#---------------------------------------------------------------------
# main frontend which proxys to the backends
#---------------------------------------------------------------------
frontend lanneluc-proxy
bind *:80
bind *:9443 ssl crt /etc/haproxy/ssl/proxy.pem no-sslv3
log global
option httplog
mode http
capture cookie SERVERID len 32
redirect scheme https if !{ ssl_fc }
maxconn 2000 # The expected number of the users of the system.
# Limits the sockets to this number of concurrent connections. Extraneous
# connections will remain in the system's backlog until a connection is
# released. If unspecified, the limit will be the same as the frontend's
# maxconn.
default_backend qm

backend qm

option forwardfor
http-request set-header X-Forwarded-Port %[dst_port]
http-request add-header X-Forwarded-Proto https if { ssl_fc }
fullconn 1000 # if not specified, HAProxy will set this
# to 10% of 'maxconn' specified on the frontend

balance leastconn
cookie SERVERID insert indirect nocache secure attr "SameSite=None"

# minconn = 100, the server will always accept at least 100,
# but no more than 'maxconn' connections. Should be the same as QM Liberty
# settings in server.xml
# maxconn = 500, the max number of connections that will be sent to a server.
# The overage will be queued. The total for all nodes should be equal to maxxcon
# on 'frontend'
server qm1 node1.host.com:9443 minconn 100 maxconn 500 ssl check cookie ccm1 verify none
server qm2 node2.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm2 verify none
server qm3 node3.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm3 verify none
server qm4 node5.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm4 verify none

# Uncomment the following section if your MessageBroker is fronted by HAProxy (for example if in High Availability mode)
#
# # connect MessageBroker cluster in tcp mode (N servers if HA mode, or a single server if IoT MessageBroker just must be fronted by proxy)
# listen MessageBroker
# bind *:1883
# mode tcp
# balance leastconn
# option tcplog
# server MessageBroker1 [MessageBroker server 1 URI]:1883 check
# server MessageBroker2 [MessageBroker server 2 URI]:1883 check
# # connect MessageBroker cluster in HTTP mode to allow gathering of MQTT statistics (6.0.6 and newer only) (N servers if HA mode, or a single server if IoT MessageBroker just must be fronted by proxy)
# listen MessageBroker_REST
# bind *:9089 ssl crt /etc/haproxy/ssl/msigh.pem no-sslv3 # Port (9089) must match that configured in MessageBroker, and the same port needs to be specified in MQTTStatsService advanced property
# mode http
# option tcp-check # Must tell HAProxy to use TCP port to do health checks
# balance leastconn
# # Same number of entries and same servers as in the section above:
# server MessageBroker_REST1 [MessageBroker server 1 URI]:9089 check port 1883 # Same ports (1883 and 9089) as used elsewhere in this file.
# server MessageBroker_REST2 [MessageBroker server 2 URI]:9089 check port 1883 # Same ports (1883 and 9089) as used elsewhere in this file.

listen statistics
bind *:1936
stats uri /
stats admin if TRUE
stats enable
stats hide-version
stats auth root:clu8ter8
stats refresh 5s

You must ensure that several important entries in the configuration file are entered correctly:
- /etc/haproxy/ssl/proxy.pem: This references the certificate that must be available to HAProxy so the proxy server can examine SSL-encrypted traffic. This ability is required for session affinity, which is an important component of clustering in .
- balance leastconn: This is the balancing strategy. The cookie SERVERID insert indirect nocache secure attr "SameSite=None" setting ensures that the user login information is passed between different sessions. Without this setting, the user will be required to log in again after navigating to any URL that requires user validation.
- Back-end servers: Replace ccmxqmx with your application names and nodex.host.com:9443 with your server URLs.
- minconn, maxconn, fullconn: The minimum connection, maximum connection, and full connection parameters.
- Administration interface:
  listen statistics
  bind *:1936
  stats uri /
  stats admin if TRUE
  stats enable
  stats hide-version
  stats auth root:clu8ter8
  stats refresh 5s
  
  These entries are explained in details in the next sections.
Open a command shell and enter the following command to enable the service:
systemctl enable haproxy
Enter the following command to start the service:
service haproxy start

II. Installing a certificate

HAProxy requires a certificate to parse encrypted traffic. You can use a self-signed certificate. The following commands create a self-signed certificate for your testing environment, but you must obtain a real certificate if required.

OpenSSL prompts you to enter the details for the certificate, such as the host name and so on. Double quotation marks are optional. The host name (CN) is the host name of the server where HAProxy is installed:

cd /usr/local/haproxy/etc
openssl genrsa -des3 -out ssl/proxy.key 2048
openssl req -new -key "ssl/proxy.key" -out "ssl/proxy.csr"
openssl x509 -req -days 365 -in "ssl/proxy.csr" -signkey "ssl/proxy.key" -out "ssl/proxy.crt"
cat ssl/proxy.crt ssl/proxy.csr > ssl/proxy.pem

III. Using a load-balancing rule

HAProxy offers several load-balancing algorithms. In the configuration example, the balance leastconn option is used. The balance leastconn option instructs HAProxy to direct traffic to the back-end server with the least number of connections.

IV. Configuring back-end servers

The back-end servers are the lines that start with "server" in the configuration file. These entries instruct the HAProxy to redirect traffic to the nodes. In the configuration example, there are four nodes. Replace the nodex.host.com parts with the actual host-name of the servers (nodes) on which you install your or servers (replicas).

You can preconfigure HAProxy with as many back-end servers (nodes) as the number of or nodes that you are planning to have. For the initial setup stage, start with one instance of or on one node by commenting out all the other server lines except for the first line:

example:

server ccm1 node1.host.com:9443 minconn 100 maxconn 500 ssl check cookie ccm1 verify none
#server ccm2 node2.host.com:9443 minconn 100 maxconn 500 ssl check cookie ccm2 verify none
#server ccm3 node3.host.com:9443 minconn 100 maxconn 500 ssl check cookie ccm3 verify none
#server ccm4 node5.host.com:9443 minconn 100 maxconn 500 ssl check cookie ccm4 verify none

QM example:

server qm1 node1.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm1 verify none
#server qm2 node2.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm2 verify none
#server qm3 node3.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm3 verify none
#server qm4 node5.host.com:9443 minconn 100 maxconn 500 ssl check cookie qm4 verify none

After HAProxy is configured, if it is running as a service, you can start, stop, and restart it by entering the following command:

sudo service haproxy start|stop|restart|reload

V. Optimizing the number of connections

The minconn, maxconn, and fullconn parameters are used to fine-tune the server and to control the number of simultaneous connections the server can handle. If more connections are established, the overage will be buffered. It can be difficult to determine the optimal numbers for these parameters, because they depend on the expected number of users and the server responsiveness, which can be influenced by available resources, network bandwidth, and so on. The number of connections can be fine-tuned depending on the number of users that are expected to use the clustered applications.

These numbers are also related to how is configured. By default, the instance that runs is configured with coreThreads="100" which is the lowest number of threads that handle incoming requests. The maximum is limited by the available system resources. Therefore, the minconn parameter should be set to the value of the coreThreads setting. The maxconn value in the back-end section (that is, one per back-end server) should be set to the maximum number of users that the server is capable of handling without showing any degradation in performance or response times. In the configuration example provided earlier, the maxconn value is set to 500 on each back end. The total of all back-end maxconn values should equal the maxconn value that is set in the front-end section of the configuration file. For example, if there are four nodes that are each set to maxconn=500, the maxconn value in the front-end should be set to 2000.

VI. Accessing the monitoring console and logs

The last section in the configuration file specifies how to access the HAProxy monitoring console. The console shows the number of nodes and their statuses, as well as the incoming and outgoing traffic. For a well-functioning cluster, assuming all nodes have been brought online at about the same time, the number of sessions (Total and lbTotal) should be roughly the same, and the number of bytes transferred should not vary too much between nodes. There should be no errors or warnings.

HAProxy maintains a log file in this directory: /var/log/haproxy.log. This log file contains information about which requests were redirected to which back-end servers and other HAProxy information such as session-affinity cookies and response codes.

Optional: Set up HAProxy high availability

Optional: Set up a custom loadbalancing

HAProxy provides different parameters for adapting and tuning its behavior, including a property named weight that you can use to identify servers for balancing. This property is only used for the first session request, because all the other requests for this session are routed to the same server with session affinity. The weight must be a value between 1 and 256. When the weight property is not set, the default value of 1 is used.

The weight property can be added to any server declaration in a back end, as shown in the following line:

backend ccm
...
server ccm1 node1.host.com:9443 minconn 100 maxconn 500 ssl check weight 50 cookie ccm1 verify none

backend qm
...
server qm1 node1.host.com:9443 minconn 100 maxconn 500 ssl check weight 50 cookie qm1 verify none

The weight parameter enables you to define a specific weight for your server. However, you must edit the haproxy.cfg file each time that you want to change the weight. To avoid opening the haproxy.cfg file to change the weight, you can use a socket interface to change the weight while the HAProxy server is running. Use the following procedure to install the Socat program, which allows you to send messages to the HAProxy TCP stats socket:

Procedure

To install Socat, enter the following command in the shell:
yum -y install socat
Open and edit the haproxy.cfg file to declare the socket and set its permission and level. Add the following lines to the general section of haproxy.cfg. In the following example, the socket in the /var/lib/haproxy/stats.sock directory is used. Only the user that is declared as the HAProxy user in the haproxy.cfg file is permitted to connect to the socket mode 600. The access level is set to administrator to allow updates to the weight parameter by using the socket:
stats socket /var/lib/haproxy/stats.sock mode 600 level admin
stats timeout 2m
Restart the HAProxy server.
Determine the correct weight for the nodes based on the server activities. You can gather system data from all nodes and compute a weight based on the gathered data. After you compute the correct weight based on system data, you can create a script and use the weight for all nodes. In the following example, ccm is the name of the back end, ccm1 is the name of the server node, and the new weight is set to 50: :
echo "set weight ccm/<serverName> <newWeight>" | socat unix-connect:/var/lib/haproxy/stats.sock stdio
ex: echo "set weight ccm/ccm1 50" | socat unix- connect:/var/lib/haproxy/stats.sock stdio
Determine the correct weight for the nodes based on the server activities. You can gather system data from all nodes and compute a weight based on the gathered data. After you compute the correct weight based on system data, you can create a script and use the weight for all nodes. In the following example, qm is the name of the back end, qm1 is the name of the server node, and the new weight is set to 50:
echo "set weight qm/<serverName> <newWeight>" | socat unix-connect:/var/lib/haproxy/stats.sock stdio
ex: echo "set weight qm/qm1 50" | socat unix- connect:/var/lib/haproxy/stats.sock stdio

Install

You can install by using Installation Manager, by extracting downloaded archive files, or by using the WebSphere Application Server Developer Tools for Eclipse. With all methods, you can also download and install assets from the Liberty Repository. See Installing Liberty.

Set up

Note: Installation of is not supported on Windows platforms.

provides secure, rapid, bidirectional messaging for the Internet of Things (IoT) and mobile environments. is a high performance MQTT broker.

I. Installing the non-Dockerized version of

Procedure

To install a non-Dockerized version of , follow these steps:

Download the required packages for the latest 1.0.0.1 or 1.1 from Eclipse Amlen download page.
Follow the instructions in the Installing the RPM on a host OS to install the non-Dockerized (RPM) version.

II. Logging in to the Web UI

For complete instructions, see the documentation.

III. Configuring

uses organizational configuration objects called hubs to define configuration policies.

Procedure

After logging in to the Web UI by following the procedure in the previous task, create a new hub and then create and assign a connection policy, messaging policy and endpoint.
Create a new connection policy. Provide a name and a description. Enter a client ID and select MQTT for protocol. Under Specify the resources that an MQTT client is permitted to consume, select Allow Clients with Durable Subscriptions and Allow Persistent Messages check boxes.
Go to the Message Policy tab and create a new topic policy. Provide a name and a description for the new topic policy. Enter a client ID and select MQTT for the protocol. In the Topic field enter an asterisk (*) and, under Authority, select both the Publish and Subscribe check boxes. Under Subscriber Settings, ensure that you enter 10000 for the Max Messages value and select Discard Old Messages for the Max Messages Behavior value.
Finally, create a new endpoint. Provide a name and a description. In the Port field, specify the port that your clients ( or nodes) use to connect to publish and subscribe to messages. Later, you will add this port to the server.startup file. Select MQTT as the protocol. Set the Max Message Size value to 4096. Under Connection Policies and Messaging Policies, add the connection policy and messaging policy (topic policy) that you created in the previous steps.

IV. Monitoring subscriptions

You can view subscription monitoring statistics by using the Web UI. To access the monitoring subscriptions, go to the Subscriptions page by selecting Monitoring > Subscriptions.

In the Monitoring view, you can see all MQTT clients (nodes), the topics being subscribed to and published, the active consumers, the number of messages, and the buffer sizes. You can use various options to filter the data.

V. Optional: high availability

To implement high availability for (primary and standby nodes), see the following topics in the documentation:

Install the server

Before you begin

Before you start the installation, complete these tasks:

Modify the response files for an external WebSphere Liberty deployment:
- Search for user.com.ibm.team.install.jfs.appserver.liberty.disable and change its value to true.
If you installed an product for trial or demonstration purposes, you must uninstall and remove any -related application directories before the new installation. For more information see, Uninstalling and the applications.
To install the servers and applications for the (), you must obtain the installation files. You can download either the Web Installer or the Installation Manager repository package for your platform from Jazz.net download section.
Obtain the installation files from the Jazz.net download area.
On IBM AIX® platforms, you can use the jar command to extract the package, but you must run the following chmod command to ensure that the Launchpad program has the correct execution permission: chmod -R +x launchpad.sh
You must have a supported version of IBM® Installation Manager for your platform. The Web Installer downloads contain Installation Manager. The easiest way to proceed is to get the Web Installer download for your platform.
You must have an Installation Manager response file that is tailored for the products to install. The Web Installer downloads contain sample response files for installing each of the available products.
You must have the Installation Manager repositories for each of the products to install. These repositories are available in the All Downloads section of the product downloads page.
Extract the downloaded .zip file to a temporary directory. To avoid issues, do not use long paths and directories that have spaces in their names. Extract any other Installation Manager repository files that you download into the same directory as the Web Installer.
The response files contain an example command-line invocation that uses the -acceptLicense argument. Before attempting a command-line installation, review the license agreement that is included in the /license directory at the top-level of the product download. Use the -acceptLicense argument on the command-line to indicate acceptance of this license agreement.
Each response file contains a line that refers to the Installation Manager repository to be used during installation. Edit the repository location attribute to point to the repository.config file in the directory that you extracted the Installation Manager repository files to.

Before you can install and run applications on your IBM AIX® system, you must increase the limit of open files:

Start smit.
Go to Security & Users > Users > Change/Show Characteristics of a User.
Enter the User ID under which the is running.
Enter a value of 65536 in the Soft NOFILE descriptors and Hard NOFILE descriptors fields.
Enter a value of 10000 in the Soft NPROC per user and Hard NPROC per user fields.
Log out and log back in to the system.
Before starting the application server, run ulimit -n and ulimit -u to see if the configuration took effect. The output for ulimit -n must be 65536 and the output for ulimit -u must be 10000.

Unless you plan to perform a silent installation, a supported browser is required to install the products with a graphical user interface and IBM Installation Manager.

The browser must be included in the $PATH environment variable. If the launchpad.sh program for IBM Installation Manager cannot find the browser, an error message will be displayed.

Before you can install and run applications on your Linux system, you must increase the limit of open files and user processes:

As a root user add the following lines to the /etc/security/limits.conf file:
* hard nofile 65536
* soft nofile 65536
* hard nproc 10000
* soft nproc 10000
If you are using REHL7, ensure that the nproc value in /etc/security/limits.d/20-nproc.conf is set to 10000.
After you modify the configuration files, restart the Linux system.
To increase the limits in a running shell, use the following commands:
ulimit -n 65536
ulimit -u 10000

Note: If you use these commands, start the Launchpad program or IBM Installation Manager from the same shell to inherit the modified limits. If you chagne this settings after is installed, reindex the server to fix any corrupted server indexes by running the Jazz_Install_Dir/server/repotools-jts -reindex repotools command.

If Security-Enhanced Linux (SELinux) is enabled, you must disable it or change the security context of the Java Runtime Environment (JRE) to allow text relocation. For more information, see Installing with Security-Enhanced Linux.

The installation path names for the applications must not contain spaces. The startup script (Jazz_Install_Dir/server/server.startup) and the repository tools script (Jazz_Install_Dir/server/repotools-app.sh) detect and report this problem.

You must have the GTK x32 libraries available in your Linux system to be able to open the Installation Manager link from the Launchpad program. For more information, see this article on jazz.net.

When you run the applications, the system can modify and write logs and other files to the installation directory. To allow all users to write to the installation directory, you must manually grant write permissions to it Jazz_Install_Dir.

About this task

There are two ways to download and install applications. The first installation method is a web-based installation that includes a smaller download and connects to the internet during the installation to get the repository files. If you must install the server in an environment without internet access, use the second installation method: download and extract the repository files to a local computer to install the server.

If you do not have User Interface libraries installed on your server or just prefer to use the command-line installation method, you can use an response file to install . This method is also referred to as silent installation.

There are two sample response files provided to install and applications:

silent-install-server.xml: Use this script to produce an installation of the applications in the C:\tmp\silent-install\JazzTeamServer/tmp/silent-install/JazzTeamServer directory that can be compressed and relocated on the file system, or to other computers with the same operating system and architecture. To use this script, you must have Installation Manager installed on your server.
silent-install-server2.xml: Use this script to install the applications in the default installation location. If you do not have Installation Manager, this script will install Installation Manager on your server before continuing with the installation.

To install , you can use the silent-install-db-server.xml sample response file.

There are two sample response files provided to install :

silent-install-jas.xml: Use this script to produce an installation of the in the C:\tmp\silent-install\JazzAuthServer/tmp/silent-install/JazzAuthServer directory that can be compressed and relocated on the file system, or to other computers with the same operating system and architecture. To use this script, you must have Installation Manager installed on your server.
silent-install-jas2.xml: Use this script to install the in the default installation location. If you do not have Installation Manager, this script will install Installation Manager on your server before continuing with the installation.

In addition to the server sample response files, these additional component sample response files are also included:

silent-install-buildsystem.xml: Installs Build System Toolkit
silent-install-client.xml: Installs - Client for Eclipse IDE
silent-install-jazz-msscci.xml: Installs MS-SCCI provider
silent-install-vs-client.xml: Installs - Client for Microsoft Visual Studio
silent-install-windows-shell-client.xml: Installs Windows Explorer Shell

Procedure

Note: Ensure that the application is already installed on the server, or you are installing it with the Architecture Management Extension at this time. If the same version of the application is not present on the server, the installation will fail.

Extract the downloaded .zip file to a temporary directory. To avoid issues, do not use long paths and directories that have spaces in their names.
Install by using either the web installer or the Installation Manager repository package.
- To install by using the web installer:
  1. Open a command prompt and change to the directory where you extracted the .zip file to, and enter launchpad. The Launchpad opens.
    
    Note: If you want to install the product as a non-root usernon-administrator user, from the Select user mode for Installation Manager list, select Non-Administrator. When you select Non-Administrator, the software packages will be installed in the user's directory and the package group will be named My . Also on Windows operating systems with User Access Control (UAC) enabled, the user who is installing the applications must be able to write to the installation directories.
  2. Follow the links in the Launchpad to continue the installation. As you follow the links in the Launchpad, Installation Manager opens to install the software packages.
- To install by using the Installation Manager repository package:
  1. Start Installation Manager.
    If you do not have a supported version of Installation Manager, you can obtain it from Jazz.net or download the web installer, which includes Installation Manager.
  2. Click File > Preferences, and then select Add Repository.
  3. To specify the repository location, browse to the directory where you downloaded the .zip file and open the repository.config file.
  4. Click OK, and then click Install to start the installation process.
  5. Follow the instructions in Installation Manager to install the software packages.
During installation, select the Install with IBM WebSphere Liberty check box.
To install the reporting components, select the check box and then on the "Select the features to install" page, expand and select the following reporting components that you want to install:
- Apache Cassandra
- Elasticsearch
During the installation of and applications for clustering, ensure that you select Enable Jazz Security Architecture SSO.
During installation, clear Install with IBM WebSphere Liberty and select the Install application WAR files check box. This is to ensure that the application WAR files are copied in the default webapps directory for later deployment. You can also choose a directory of your choice to copy the WAR files.
To install , from the launchpad menu under Install additional servers, select Install . Follow the steps in the Installation Manager wizard to install . For information about starting , see Deploying and starting .
To install , from the launchpad menu under Install additional servers, select Install . Follow the steps in the Installation Manager wizard to install . For information about , see Reporting with .

Note: If you are planning to use the System for Cross-domain Identity Management (SCIM) standard, you must install and configure the . The link to install the is available in the Launchpad program.

Note: You can install on the same computer as or on its own dedicated server. Install on the computer that you identified as your , and install the clustered applications on the computer corresponding to the node you have enabled in your HAProxy configuration.

Open a command prompt and change to the ExtractedDir\im\win32.win32.x86 directory.
Open a command shell and change to the ExtractedDir/im/linux.gtx.x86 directory.
Open a command shell and change to the ExtractedDir/im/linux.gtx.ppc directory.
Open a command shell and change to the ExtractedDir/im/linux.gtx.s390 directory.
Open a command shell and change to the ExtractedDir/im/aix.motif.ppc directory.
To install the applications as an administrator into a shared area, use the installc variant in the following command:
.\installc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini silent-install.ini

./installc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini silent-install.ini
To install the applications into a user-specific location use the userinstc variant in the following command:
.\userinstc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini user-silent-install.ini

./userinstc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini user-silent-install.ini
To install as an administrator into a shared area, use the installc variant in the following command:
.\installc -acceptLicense -showVerboseProgress -input silent-install-jas2.xml --launcher.ini silent-install.ini

./installc -acceptLicense -showVerboseProgress -input silent-install-jas2.xml --launcher.ini silent-install.ini
To install into a user-specific location use the userinstc variant in the following command:
.\userinstc -acceptLicense -showVerboseProgress -input silent-install-jas2.xml --launcher.ini user-silent-install.ini

./userinstc -acceptLicense -showVerboseProgress -input silent-install-jas2.xml --launcher.ini user-silent-install.ini
To install as an administrator, use the installc variant in the following command:
.\installc -acceptLicense -showVerboseProgress -input silent-install-db-server.xml --launcher.ini silent-install.ini

./installc -acceptLicense -showVerboseProgress -input silent-install-db-server.xml --launcher.ini silent-install.ini
To install as a non-administrator, use the userinstc variant in the following command:
.\userinstc -acceptLicense -showVerboseProgress -input silent-install-db-server.xml --launcher.ini silent-install.ini

./userinstc -acceptLicense -showVerboseProgress -input silent-install-db-server.xml --launcher.ini silent-install.ini

By default, the response files are configured for deploying ELM on an embedded IBM WebSphere Liberty server. To modify the response files for an external IBM WebSphere Liberty deployment, complete the following steps:

Open silent-install-server.xml and search for user.com.ibm.team.install.jfs.appserver.liberty.disable and change its value to true.
Complete the set up after installation. See, .

To remove an application from being installed, search for the application name and comment out or delete the line. For example, if you do not want to install application, search for rtc and delete or comment out the offering line:

By default, the jrs offering installs all reporting features. If you want to install a subset of features, add a features parameter and list the features that you want to install separated by commas, for example:

Installing the server on IBM i

For step-by-step instructions for new installations of , see Installing and applications on IBM i.

For detailed instructions for installing the Build System Toolkit, see Installing the Build System Toolkit on IBM i systems.

Installing the server on IBM i

Configuring ELM on stand-alone IBM WebSphere Liberty Server

ELM is shipped with an embedded IBM WebSphere Liberty server to ease the installation process. However, you can also deploy ELM applications on a stand-alone IBM WebSphere Liberty server. There are certain configurations that you need to do to deploy ELM on stand-alone IBM WebSphere Liberty server.

Navigate to the Server folder.
For example, if the ELM applications are installed at C:\ELM_Liberty_Setup\JazzTeamServer_1 location. The Server folder is available within the JazzTeamServer_1 folder.

For example, if the ELM applications are installed at /opt/IBM/JazzTeamServer_1 location. The Server folder is available within the JazzTeamServer_1 folder.
Update value of the following properties in the liberty.server.bat liberty.server.sh file:
- The CLM_LIBERTY_HOME property must point to the Liberty folder of the WebSphere Liberty server. For the example, the WebSphere Liberty server is installed at C:\Program Files\IBM\WebSphere\Liberty property must be: CLM_LIBERTY_HOME=C:\Program Files\IBM\WebSphere\Liberty
- The CLM_LIBERTY_SERVER_DIR property must point to the servers folder in the WebSphere Liberty server you recently installed. For example, CLM_LIBERTY_SERVER_DIR=C:\Program Files\IBM\WebSphere\Liberty\usr\servers\%CLM_LIBERTY_SERVER_NAME%
- The WLP_USER_DIR property must point to the WebSphere Liberty server user directory. For example, WLP_USER_DIR=C:\Program Files\IBM\WebSphere\Liberty\usr
- Optional: The CLM_LIBERTY_SERVER_NAME property to change the name of the server. For example, CLM_LIBERTY_SERVER_NAME=clm
- Optional: The CLM_LIBERTY_SERVER_TEMPLATE property to move the ELM server template to the new WebSphere Liberty server. For example, CML_LIBERTY_SERVER_TEMPLATE=C:\Program Files\IBM\WebSphere\Liberty\templates\clmServerTemplate
- The CLM_LIBERTY_HOME property must point to the Liberty folder of the WebSphere Liberty server. For the example, the WebSphere Liberty server is installed at /opt/IBM/WebSphere/Liberty property must be: CLM_LIBERTY_HOME=/opt/IBM/WebSphere/Liberty
- The CLM_LIBERTY_SERVER_DIR property must point to the servers folder in the WebSphere Liberty server you recently installed. For example, CLM_LIBERTY_SERVER_DIR=/opt/IBM/WebSphere/Liberty/usr/servers/%CLM_LIBERTY_SERVER_NAME%
- The WLP_USER_DIR property must point to the WebSphere Liberty server user directory. For example, WLP_USER_DIR=/opt/IBM/WebSphere/Liberty/usr
- Optional: The CLM_LIBERTY_SERVER_NAME property to change the name of the server. For example, CLM_LIBERTY_SERVER_NAME=clm
- Optional: The CLM_LIBERTY_SERVER_TEMPLATE property to move the ELM server template to the new WebSphere Liberty server. For example, CML_LIBERTY_SERVER_TEMPLATE=C:\Program Files\IBM\WebSphere\Liberty\templates\clmServerTemplate
Optional: If you want to use the WebSphere Liberty server's JRE instead of the ELM server's JRE, you must update the following properties in the server.startup.bat and server.shutdown.bat files:
- The JAVA_HOME property should point to the Java directory of the WebSphere Liberty server. For example, JAVA_HOME=C:\Program Files\IBM\WebSphere\Liberty\java\11.0 JAVA_HOME=/opt/IBM/WebSphere/Liberty/java/11.0
- The JRE_HOME property should point to the jre directory of the WebSphere Liberty server. For example, JRE_HOME=C:\Program Files\IBM\WebSphere\Liberty\java\11.0\jre JRE_HOME=/opt/IBM/WebSphere/Liberty/java/11.0/jre
Open the command prompt and navigate to the ELM server directory.
1. Run the server.startup.batserver.startup.sh file to start the ELM server.
After the server has started, a new folder for ELM server is created in the servers directory of the WebSphere Liberty server. For example, if the WebSphere Liberty server is installed at the C:\Program Files\IBM\WebSphere\Liberty direcotry, the ELM folder is created at C:\Program Files\IBM\WebSphere\Liberty\usr\servers\clm.

After the server has started, a new folder for ELM server is created in the servers directory of the WebSphere Liberty server. For example, if the WebSphere Liberty server is installed at the /opt/IBM/WebSphere/Liberty directory, the ELM folder is created at /opt/IBM/WebSphere/Liberty/usr/servers/clm.
Run the server.shutdown.batserver.shutdown.sh file to shutdown the ELM server.

Set up the database

Before you create databases for your clustered environment, ensure that theread and write caches are enabled for the disk configuration.

Open the /etc/security/limits.conf file and set the following ulimits parameters:

<dbuser> hard nofile 65536
<dbuser> soft nofile 65536
<dbuser> hard nproc 65536
<dbuser> soft nproc 65536

If you are using the included Derby database, no additional setup is necessary. Proceed with the next step.

Note: Although a Derby database is included in the default configuration and requires no installation, this database is limited to 10 users. To enable more users, install a supported enterprise database such as Db2, Oracle, or SQL Server.

To create database tables, see Creating Db2 for z/OS database tables remotely.

By default, IBM Db2i database is setup and configured on your IBM i system. No additional setup is necessary. Proceed with the next step.

The products support IBM Db2 Standard Edition and Advanced Edition. You can obtain Db2 Standard Edition from this ELM release’s Optional Programs page on jazz.net or from IBM Passport Advantage downloads as part of your ELM product(s).

Before you begin

This procedure requires that the following prerequisites are met:

You have the correct user password. On the UNIX systems, get the password for the Db2 instance owner, which is typically the db2inst1 user.
You have reviewed the Db2 documentation to verify that your system meets the requirements and is configured correctly.
Db2 is installed and running on a computer to be used as the database server. This computer can be different from the one that the runs on.
The user in the teamserver.properties file has system administrator authority over the database. For information about preparing a Db2 database with only DBADM authority, see this wiki page.

Procedure

database

Open a Db2 command window.
Enter this command to create a database for called JTS with 16K pages and the UTF-8 code set:
db2 create database JTS using codeset UTF-8 territory en PAGESIZE 16384

database

Open a Db2 command window.
Enter this command to create a database for called PUB with 16K pages and the UTF-8 code set:
db2 create database PUB using codeset UTF-8 territory en PAGESIZE 16384

database

Create a file called createOauthTablesDB2.sql. Refer to the following SQL example to create the database and tables for . You can use a different database name than oauth2db, but you must use the OAuthDBSchema schema.
Also note that these values are examples and you should change them according to your usage and environment. For example, if the TOKENSTRING value of 2048 is too small, you can increase that by using a datatype of TOKENSTRING NVARCHAR(MAX) NOT NULL,.

CREATE DATABASE oauth2db USING CODESET UTF8 TERRITORY US;
CONNECT TO oauth2db;

CREATE BUFFERPOOL BUFF16K IMMEDIATE SIZE 2500 AUTOMATIC PAGESIZE 16K;
create tablespace TAB16K pagesize 16K bufferpool BUFF16K dropped table recovery on;
CREATE SYSTEM TEMPORARY TABLESPACE TEMPSYS16K PAGESIZE 16K BUFFERPOOL BUFF16K;

---- CREATE TABLES ----
CREATE TABLE OAuthDBSchema.OAUTH20CACHE
(
LOOKUPKEY VARCHAR(256) NOT NULL,
UNIQUEID VARCHAR(128) NOT NULL,
COMPONENTID VARCHAR(256) NOT NULL,
TYPE VARCHAR(64) NOT NULL,
SUBTYPE VARCHAR(64),
CREATEDAT BIGINT,
LIFETIME INT,
EXPIRES BIGINT,
TOKENSTRING VARCHAR(2048) NOT NULL,
CLIENTID VARCHAR(64) NOT NULL,
USERNAME VARCHAR(64) NOT NULL,
SCOPE VARCHAR(512) NOT NULL,
REDIRECTURI VARCHAR(2048),
STATEID VARCHAR(64) NOT NULL,
EXTENDEDFIELDS CLOB NOT NULL DEFAULT '{}'
);

CREATE TABLE OAuthDBSchema.OAUTH20CLIENTCONFIG
(
COMPONENTID VARCHAR(256) NOT NULL,
CLIENTID VARCHAR(256) NOT NULL,
CLIENTSECRET VARCHAR(256),
DISPLAYNAME VARCHAR(256) NOT NULL,
REDIRECTURI VARCHAR(2048),
ENABLED INT,
CLIENTMETADATA CLOB NOT NULL DEFAULT '{}'
);

CREATE TABLE OAuthDBSchema.OAUTH20CONSENTCACHE (
CLIENTID VARCHAR(256) NOT NULL,
USERID VARCHAR(256),
PROVIDERID VARCHAR(256) NOT NULL,
SCOPE VARCHAR(1024) NOT NULL,
EXPIRES BIGINT,
EXTENDEDFIELDS CLOB NOT NULL DEFAULT '{}'
);

---- ADD CONSTRAINTS ----
ALTER TABLE OAuthDBSchema.OAUTH20CACHE
ADD CONSTRAINT PK_LOOKUPKEY PRIMARY KEY (LOOKUPKEY);

ALTER TABLE OAuthDBSchema.OAUTH20CLIENTCONFIG
ADD CONSTRAINT PK_COMPIDCLIENTID PRIMARY KEY (COMPONENTID,CLIENTID);

---- CREATE INDEXES ----
CREATE INDEX OAUTH20CACHE_EXPIRES ON OAUTHDBSCHEMA.OAUTH20CACHE (EXPIRES ASC);

---- GRANT PRIVILEGES ----
---- UNCOMMENT THE FOLLOWING IF YOU USE AN ACCOUNT OTHER THAN ADMINISTRATOR FOR DB ACCESS ----

-- Change dbuser to the account you want to use to access your database
-- GRANT ALL ON OAuthDBSchema.OAUTH20CACHE TO USER dbuser;
-- GRANT ALL ON OAuthDBSchema.OAUTH20CLIENTCONFIG TO USER dbuser;

---- END OF GRANT PRIVILIGES ----

DISCONNECT CURRENT;
Open a Db2 command window and run the following script to create the database, tables, and indexes, and to grant privileges:
db2 -stvf createOauthTablesDB2.sql
After creating the database tables, you must configure to use the tables. Go to C:\IBM\JazzAuthServer\wlp\usr\servers\jazzop/opt/IBM/JazzAuthServer/wlp/usr/servers/jazzop and open appConfig.xml for editing.
Comment out the following Apache Derby database section:
<dataSource id=OAuthFvtDataSource jndiName=jdbc/OAuth2DB>
<jdbcDriver libraryRef=DerbyLib />
<properties.derby.embedded
databaseName=asDB
createDatabase=create />
</dataSource>

<library id=DerbyLib>
<fileset dir=${shared.config.dir}/lib/global includes=derby.jar />
</library>
Add the following section to configure a Db2 database. You must customize this section to work with your specific Db2 server:
<jdbcDriver id=db2Universal libraryRef=DB2JCC4LIB/>
<library id=DB2JCC4LIB filesetRef=db2jcc4 apiTypeVisibility=spec,ibm-api,third-party/>
<fileset dir=${shared.config.dir}/lib/global id=db2jcc4 includes=db2jcc4.jar db2jcc_license_cu.jar/>
<dataSource id=OAUTH2DBDS jndiName=jdbc/oauthProvider jdbcDriverRef=db2Universal>
<properties.db2.jcc password=***** databaseName=OAUTH2DB user=db2inst1 portNumber=50000 serverName=yourDB2.com driverType=4/>
</dataSource>

Ensure that you have the correct values for the following attributes:
- For user, provide the name of the Db2 user that is used to connect to the database.
- For password, use the Db2 user password.
- For databaseName, use the database name you created in the previous step. If you used the sample script file, the database name is OAUTH2DB.
- For portNumber, use the port number that the Db2 instance is running on. The default port number is 50000.
- For serverName, enter the host name of the Db2 server.
In the oauthProvider section of the appConfig.xml file, update the databaseStore property so it specifies the Db2 data source rather than the default Apache Derby data source. The databaseStore property should specify the name of the DB2 data source, which in this example, is OAUTH2DBDS:
<oauthProvider id=JazzOP
httpsRequired=true
autoAuthorize=true
customLoginURL=/jazzop/form/login
accessTokenLifetime=7201
authorizationGrantLifetime=604801>
<autoAuthorizeClient>client01</autoAuthorizeClient>
<databaseStore dataSourceRef=OAUTH2DBDS />
</oauthProvider>
Save and close the appConfig.xml file.
Copy the Db2 db2jcc4.jar and db2jcc_license_cu.jar JDBC drivers from your Db2 server to this directory: C:\IBM\JazzAuthServer\wlp\usr\shared\config\lib\globalopt/IBM/JazzAuthServer/wlp/usr/shared/config/lib/global.

database

Open a Db2 command window.
Enter this command to create a database for application called with 16K pages and the UTF-8 code set:
db2 create database using codeset UTF-8 territory en PAGESIZE 16384

database

Open Db2 command window.
Enter this command to create a database for application called QM with 16K pages and the UTF-8 code set:
db2 create database QM using codeset UTF-8 territory en PAGESIZE 16384

database

Open a Db2 command window.
Enter this command to create a database for application called RM with 16K pages and the UTF-8 code set:
db2 create database RM using codeset UTF-8 territory en PAGESIZE 16384

database

Open a Db2 command window.
Enter this command to create a database for the application called DCC with 16K pages and the UTF-8 code set:
db2 create database DCC using codeset UTF-8 territory en PAGESIZE 16384

database

Open a Db2 command window.
Enter this command to create a database for the application called LQE with 32K pages and the UTF-8 code set:
Note: The database requires 32K pages.

db2 create database LQE using codeset UTF-8 territory en PAGESIZE 32768

The LQE database must have the MAXAPPLS increased to allow for concurrent connections in to process data if it is not set to AUTOMATIC. Increase the value to 300:

db2 update db cfg for LQE using maxappls 300

This means that the lock list must also be increased if it is not set to AUTOMATIC:

db2 update db cfg FOR LQE using locklist 20000

The transaction logs will also grow as data is processed in parallel. Increase the LOGFILSIZ to 20000:

db2 update db cfg for LQE using LOGFILSIZ 20000

Increase the number of primary and secondary transactions log files:

db2 update db cfg for LQE using logprimary 25
db2 update db cfg for LQE using logsecond 100

database

Open a Db2 command window.
Enter this command to create a database for the application called LDX with 32K pages and the UTF-8 code set:
Note: The database requires 32K pages.

db2 create database LDX using codeset UTF-8 territory en PAGESIZE 32768

database

Open a Db2 command window.
Enter this command to create a database for the Global Configuration application called GC with 16K pages and the UTF-8 code set:
db2 create database GC using codeset UTF-8 territory en PAGESIZE 16384

database

Open a Db2 command window.
Enter this command to create a database for the application called with 16K pages and the UTF-8 code set:
db2 create database using codeset UTF-8 territory en PAGESIZE 16384

Data warehouse database

Open a Db2 command window.
Enter this command to create a database for your data warehouse called DW with 32K pages and the UTF-8 code set:
db2 create database DW using codeset UTF-8 territory en PAGESIZE 32768

The data warehouse database must have the MAXAPPLS increased to allow for concurrent connections in to process data if it is not set to AUTOMATIC. Increase the value to 300:

db2 update db cfg for DW using maxappls 300

This means that the lock list must also be increased if it is not set to AUTOMATIC:

db2 update db cfg FOR DW using locklist 20000

The transaction logs will also grow as data is processed in parallel. Increase the LOGFILSIZ to 20000:

db2 update db cfg for DW using LOGFILSIZ 20000

Increase the number of primary and secondary transactions log files:

db2 update db cfg for DW using logprimary 25
db2 update db cfg for DW using logsecond 200

DBADM authority

If you are creating the database with a user other than the user specified in the teamserver.properties file, you must grant DBADM authority to that user:

db2 connect to database_name
db2 grant dbadm on database to user user_name
db2 disconnect database_name

Verify

If you create all databases on the same database server, verify that the Max number of concurrently active databases is set to a number greater than the number of databases you created. If this value is lower than the number of active databases, you will get the SQL Code 1041 error.

To verify the value and increase the number if necessary, complete these steps:

Open a Db2 command window and enter this command to display the database manager configuration:
db2 get dbm cfg
Look for the Max number of concurrently active databases line. If this number is lower than the installed databases, increase the number by entering this command:
db2 update dbm cfg using numdb 32
Stop and start the database manager for these changes to take effect by entering these commands:
db2stop
db2start

To create and set up an Oracle database, it is assumed that the user who is preparing the database has database administration authority over the database and that the database, tablespace storage, and appropriate storage configuration is created by a user with system administration authority.

Before you begin

The required Java Database Connectivity (JDBC) driver is ojdbc8.jar. For a list of supported database versions and driver versions, see the system requirements link in the Planning checklist section of this document.

Restriction: Because of a defect in Oracle JDBC driver 12.1.0.2.0, this version of the driver cannot be used. For details, see repotools -createTables command fails with ORA-01000 on Oracle 12 on the IBM Support portal page.

The configuration parameters and tablespace options used in this step are examples and might not entirely apply to your environment. For example, if you cannot use the AUTOEXTEND setting, then the files must be large enough to allow for growth. Or if you cannot use the UNLIMITED size quota for the database user, then make sure to allow enough space for rapid growth.
If you install the () applications on the same computer or distributed platforms, you can either create separate databases for each application or you can use the same database for all applications. However, you must create a separate tablespace and a database user who is associated with that tablespace for each application.
The examples in this step are for one Oracle database with separate tablespaces and database users who are dedicated to each application.
The database that you create for the and all applications must be formatted to use UTF-8 as the character set. By default, Oracle does not create a database with the UTF-8 character set. When you create a new database, ensure that you select AL32UTF8 in the Oracle DB setup.
Change the open cursors limit:
- If you use spfile to start the database, open a SQL *Plus window and enter the following command:
  alter system set open_cursors = 10000 scope=both;
- If you use pfile to start the database, open a SQL *Plus window and enter the following command:
  alter system set open_cursors = 10000;

For the Oracle data warehouse database to work efficiently with the , you must increase the PROCESSES configuration to 3000.

Procedure

Create an Oracle database

As a system administrator, create a database with UTF-8 encoding for and all applications.

Start the Database Configuration Assistant wizard and on the Welcome page click Next.
On the Operations page, select Create a Database and then click Next.
On the Templates page, select Custom Database and click Next.
In both the Global Database Name and SID fields, enter a name for the content storage database, for example, DB. Click Next.
To configure the database control, enter the required information for alert notification and optionally enable the daily disk backup schedule. To continue without database control configuration, clear the check box next to Configure Enterprise Manager and then click Next.
On the Database Credentials page, choose an option for your user account, and then click Next.
Note: Oracle password complexity policy requires that passwords should have minimum of 12 characters in length. In addition, the password must contain at least one upper-case character, one lower-case character, and one digit. If your password contains special characters, multibyte characters, or starts with numbers or special characters, you must enclose it in double quotation marks. For details, see the Oracle documentation.
On the next page, select a storage type and location for database files. Click Next.
On the next page, choose a recovery option for the database, and then click Next.
On the next page, specify whether or not to add the Sample Schemas to your database. Click Next.
On the next page, click the Character Sets tab and select Use Unicode (AL32UTF8). Click Next.
Note: Setting character set to Unicode (AL32UTF8) enables you to store multiple language groups.
On the Database Storage page verify or change the database objects and click Next.
On the next page click Finish to create the database.
On the Confirmation window that opens, optionally save the page as an HTML file, and then click OK. A progress bar is displayed to show the database creation progress.

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for , enter the following command. Replace JTS with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in previous step, and JTS.DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE JTS
DATAFILE 'ORACLE_BASE/oradata/DB/JTS.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for , enter the following command. Replace JTS_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in previous step, and JTS_TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE JTS_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/JTS_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for , enter the following command. Replace PUB with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in previous step, and PUB.DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE PUB
DATAFILE 'ORACLE_BASE/oradata/DB/PUB.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for , enter the following command. Replace PUB_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in previous step, and PUB_TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE PUB_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/PUB_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for

Create a file called createOauthOracle.sql. Refer to the following SQL example to create the tablespaces required for .
Note that the values in the script file are examples and you should change them according to your usage and environment. For example, if the TOKENSTRING value of 2048 is too small, you can increase that by using a datatype of TOKENSTRING NVARCHAR(MAX) NOT NULL,.

createOauthOracle.sql creates two tablespaces: OAUTH and OAUTH_TMP, and creates the tables in the OAUTH tablespace. If you have an existing tablespace that you want to use, you can change the CREATE TABLE statement to use your existing tablespace. If you want to create new tablespaces, then you should edit the DATAFILE and TEMPFILE clauses to point at the directory that you want to use for the tablespace.

expects to find a user named OAUTHDBSCHEMA, and it expects to find tables in a schema named OAUTHDBSCHEMA. You must create the OAUTHDBSCHEMA user in Oracle. Customize the CREATE USER statement to specify a password for the OAUTHDBSCHEMA user. When you create the OAUTHDBSCHEMA user, you must also associate that user with the tablespace you plan to use for the OAUTH tables.

CREATE TABLESPACE OAUTH DATAFILE '/home/oracle/tablespaces/OAUTH.dbf' SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE OAUTH_TMP TEMPFILE '/home/oracle/tablespaces/OAUTH_TMP.dbf' SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE USER OAUTHDBSCHEMA IDENTIFIED BY <your password> DEFAULT TABLESPACE OAUTH QUOTA UNLIMITED ON OAUTH TEMPORARY TABLESPACE OAUTH_TMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO OAUTHDBSCHEMA;

---- CREATE TABLES ----
CREATE TABLE OAuthDBSchema.OAUTH20CACHE
(
LOOKUPKEY VARCHAR(256) NOT NULL,
UNIQUEID VARCHAR(128) NOT NULL,
COMPONENTID VARCHAR(256) NOT NULL,
TYPE VARCHAR(64) NOT NULL,
SUBTYPE VARCHAR(64),
CREATEDAT NUMBER(19,0),
LIFETIME INT,
EXPIRES NUMBER(19,0),
TOKENSTRING VARCHAR(2048) NOT NULL,
CLIENTID VARCHAR(64) NOT NULL,
USERNAME VARCHAR(64) NOT NULL,
SCOPE VARCHAR(512) NOT NULL,
REDIRECTURI VARCHAR(2048),
STATEID VARCHAR(64) NOT NULL,
EXTENDEDFIELDS CLOB DEFAULT '{}' NOT NULL
)
TABLESPACE OAUTH STORAGE(INITIAL 50K);

CREATE TABLE OAuthDBSchema.OAUTH20CLIENTCONFIG
(
COMPONENTID VARCHAR(256) NOT NULL,
CLIENTID VARCHAR(256) NOT NULL,
CLIENTSECRET VARCHAR(256),
DISPLAYNAME VARCHAR(256),
REDIRECTURI VARCHAR(2048),
ENABLED INT,
CLIENTMETADATA CLOB DEFAULT '{}' NOT NULL
) TABLESPACE OAUTH STORAGE(INITIAL 50K);

CREATE TABLE OAuthDBSchema.OAUTH20CONSENTCACHE (
CLIENTID VARCHAR(256) NOT NULL,
USERID VARCHAR(256),
PROVIDERID VARCHAR(256) NOT NULL,
SCOPE VARCHAR(1024) NOT NULL,
EXPIRES NUMBER(19,0),
EXTENDEDFIELDS CLOB DEFAULT '{}' NOT NULL
) TABLESPACE OAUTH STORAGE(INITIAL 50K);

---- ADD CONSTRAINTS ----
ALTER TABLE OAuthDBSchema.OAUTH20CACHE
ADD CONSTRAINT PK_LOOKUPKEY PRIMARY KEY (LOOKUPKEY);

ALTER TABLE OAuthDBSchema.OAUTH20CLIENTCONFIG
ADD CONSTRAINT PK_COMPIDCLIENTID PRIMARY KEY (COMPONENTID,CLIENTID);

---- CREATE INDEXES ----
CREATE INDEX OAUTH20CACHE_EXPIRES ON OAuthDBSchema.OAUTH20CACHE (EXPIRES ASC);

---- GRANT PRIVILEGES ----
---- UNCOMMENT THE FOLLOWING IF YOU USE AN ACCOUNT OTHER THAN ADMINISTRATOR FOR DB ACCESS ----

-- Change dbuser to the account you want to use to access your database
GRANT ALL ON OAuthDBSchema.OAUTH20CACHE TO OAUTHDBSCHEMA;
GRANT ALL ON OAuthDBSchema.OAUTH20CLIENTCONFIG TO OAUTHDBSCHEMA;
GRANT ALL ON OAuthDBSchema.OAUTH20CONSENTCACHE TO OAUTHDBSCHEMA;

---- END OF GRANT PRIVILIGES ----
After you finish customizing the createOauthOracle.sql script, open SQL Plus and log in as SYSDBA, and run the SQL script:
@createOauthOracle.sql
After creating the database tables, you must configure to use the tables. Go to C:\IBM\JazzAuthServer\wlp\usr\servers\jazzop/opt/IBM/JazzAuthServer/wlp/usr/servers/jazzop and open appConfig.xml for editing.
Comment out the following Apache Derby database section:
<dataSource id=OAuthFvtDataSource jndiName=jdbc/OAuth2DB>
<jdbcDriver libraryRef=DerbyLib />
<properties.derby.embedded
databaseName=asDB
createDatabase=create />
</dataSource>

<library id=DerbyLib>
<fileset dir=${shared.config.dir}/lib/global includes=derby.jar />
</library>
Add the following section to configure Oracle. You must customize this section to work with your specific Oracle server:
<dataSource id=OAUTH2ORA jndiName=jdbc/OAuth2DB>
<jdbcDriver id=oracle libraryRef=ORAJCC4LIB/>
<library id=ORAJCC4LIB filesetRef=orajcc4 apiTypeVisibility=spec,ibm-api,third-party/>
<fileset dir=${shared.config.dir}/lib/global id=orajcc4 includes=ojdbc8.jar/>
<dataSource id=OAUTH2ORA jndiName=jdbc/oauthProvider jdbcDriverRef=oracle>
<properties.oracle password=***** databaseName=ORCL user=OAUTHDBSCHEMA portNumber=1521 serverName=yourOracle.com/>
</dataSource>

Ensure that you have the correct values for the following attributes:
- For password, use the password you specified when creating the OAUTHDBSCHEMA user in Oracle.
- For databaseName, use the Oracle SID for your database. The sample uses the default value assigned by Oracle - ORCL. Your value might be different.
- For portNumber, use the port number that the Oracle instance is running on. The default port number is 1521.
- For serverName, enter the host name of the Oracle server.
In the oauthProvider section of the appConfig.xml file, update the databaseStore property so it specifies the Oracle data source rather than the default Apache Derby data source. The databaseStore property should specify the name of the Oracle data source, which in this example, is OAUTH2ORA:
<oauthProvider id=JazzOP
httpsRequired=true
autoAuthorize=true
customLoginURL=/jazzop/form/login
accessTokenLifetime=7201
authorizationGrantLifetime=604801>
<autoAuthorizeClient>client01</autoAuthorizeClient>
<databaseStore dataSourceRef=OAUTH2ORA />
</oauthProvider>
Save and close the appConfig.xml file.
Copy the Oracle ojdbc8.jar JDBC drivers from your Oracle server to this directory: C:\IBM\JazzAuthServer\wlp\usr\shared\config\lib\globalopt/IBM/JazzAuthServer/wlp/usr/shared/config/lib/global.

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for the application, enter the following command. Replace with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and .DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE
DATAFILE 'ORACLE_BASE/oradata/DB/.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for the application, enter the following command. Replace _TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in previous step, and _TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE _TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for the application, enter the following command. Replace with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and .DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE
DATAFILE 'ORACLE_BASE/oradata/DB/.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for the application, enter the following command. Replace _TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and _TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE _TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for the application, enter the following command. Replace QM with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and QM.DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE QM
DATAFILE 'ORACLE_BASE/oradata/DB/QM.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for the application, enter the following command. Replace QM_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and QM_TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE QM_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/QM_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for the application, enter the following command. Replace RM with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and RM.DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE RM
DATAFILE 'ORACLE_BASE/oradata/DB/RM.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for the application, enter the following command. Replace RM_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and RM_TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE RM_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/RM_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for the application, enter the following command. Replace DCC with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and DCC.DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE DCC
DATAFILE 'ORACLE_BASE/oradata/DB/DCC.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for the application, enter the following command. Replace DCC_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and DCC_TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE DCC_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/DCC_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for the application, enter the following command. Replace LQE with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and LQE.DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE LQE
DATAFILE 'ORACLE_BASE/oradata/DB/LQE.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for the application, enter the following command. Replace LQE_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and LQE_TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE LQE_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/LQE_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for the application, enter the following command. Replace LDX with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and LDX.DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE LDX
DATAFILE 'ORACLE_BASE/oradata/DB/LDX.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for the application, enter the following command. Replace LDX_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and LDX_TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE LDX_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/LDX_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for the Global Configuration application, enter the following command. Replace GC with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and GC.DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE GC
DATAFILE 'ORACLE_BASE/oradata/DB/GC.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for the Global Configuration application, enter the following command. Replace GC_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and GC_TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE GC_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/GC_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create tablespaces for Data Warehouse

Start SQL Plus and log in as SYSTEM or SYSDBA.
To create a tablespace for the common data warehouse, enter the following command. Replace DW with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and DW.DBF with the datafile name that you want to create.

CREATE BIGFILE TABLESPACE DW
DATAFILE 'ORACLE_BASE/oradata/DB/DW.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

To create a temporary tablespace for the common data warehouse, enter the following command. Replace DW_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, DB with the database name you created in step a, and DW_TEMP.DBF with the temporary file name that you want to create.

CREATE TEMPORARY TABLESPACE DW_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/DW_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Verify

In the Oracle Enterprise Manager Database Control, click Server > Tablespaces and verify that the tablespaces you created are displayed and accessible. Also ensure that the default Oracle tablespace named USERS already exist. If this tablespace does not exist in your Oracle database, create it.

Create an Oracle database user for each new tablespace

After the tablespaces are created, a special Oracle user must be created for each application to use the Oracle database. For multiple Jazz servers that run on one Oracle database, an Oracle database user must be created for each application. The Oracle database user must be able to create database objects in its tablespace (either unlimited or with a space quota) with privileges to create session, table, procedure, and views.

To create a user for tablespace and to grant the required permissions, enter the following commands:

CREATE USER JTS_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE JTS QUOTA UNLIMITED ON JTS TEMPORARY TABLESPACE JTS_TEMP;

GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO JTS_DB_USER;

To create a user for tablespace and to grant the required permissions, enter the following commands:

CREATE USER PUB_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE PUB QUOTA UNLIMITED ON PUB TEMPORARY TABLESPACE PUB_TEMP;

GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO PUB_DB_USER;