This article describes a step-by-step procedure to integrate PureData System for Transactions (hereafter called PureData) with PureApplication System (hereafter called PureApplication). This procedure allows you to use a database from PureData for existing or new patterns of PureApplication. The benefits of this procedure are:
- Mission critical data: PureApplication and PureData integration enable your business to deploy optimized and continuously available mission critical databases when you use these databases in PureApplication middleware applications.
- High availability of transactional data for PureApplication: PureData can provide built-in database clusters that spread across multiple cluster nodes. DB2® pureScale™ provides unlimited capacity, load balancing, and application transparency. This feature keeps your data available all the time. PureApplication as the solution frontend and PureData for the backend work together as a combined platform. PureApplication provides a high availability (HA) proxy server, application server, and caching server for applications deployed in this platform. PureData provides a highly available database server and storage resources for the platform.
- Speed: PureApplication is a highly efficient platform for applications deployment. When you use PureApplication and PureData together, you can specify the requirements, such as when applications demand higher levels of scalability, availability, and performance. This solution allows you to easily and dynamically increase performance.
- On-demand resource allocation: PureApplication is a complete system platform of hardware and middleware. You drop applications into the system's pre-configured middleware engine that includes an IBM DB2 database and IBM WebSphere® Application Server. You can dynamically adjust to demand spikes and reallocate the system resources automatically. Multiple applications and database patterns are provided, as part of the system, for optimally deploying and managing applications and resources in virtual and cloud environments.
- Consolidating the database server for applications: These systems provide database server consolidation. You do not need to worry about managing individual database servers. A single interface makes it easier to manage the databases that are used by many applications.
- Scalability: This system integration also provides non-disruptive scalability. Administrators can add more nodes with no application changes required. You can start small and easily grow, with no need to over-purchase or over-provision.
Before integrating PureData with PureApplication, you will need to complete the following steps. Note that the physical connection and SSL certificates need to be done by the IBM Customer Engineer (CE).
- Configure the connection between PureData and PureApplication.
- Configure the network communication between PureData and PureApplication.
- Configure the trusted certificate between PureData and PureApplication.
- Register PureData with PureApplication.
- Configure administrator access to the PureApplication System Workload Console.
- Configure the existing user ID and password information for PureData.
- To use PureData, users must have a security administration role.
Registering PureData with PureApplication
To register PureData with PureApplication:
- Open the PureApplication Web console, such as
https://<IP-Address or hostname>.
- Click the Workload Console tab at the top of the Welcome page to open the Workload console on PureApplication.
- Click the drop-down list of the System tab.
- From the list, select PureData System registration.
- Fill in the IP address, user name, and user password for the PureData fields as shown in Figure 1.
Figure 1. PureApplication System Web Console
Creating a pureScale database pattern
To create a pureScale database pattern using PureApplication from PureData:
- Open the PureApplication System Console, such as
https:<IP-Address or hostname>.
- Click on the Workload Console.
- On the Workload Console page, expand the
Working with databases section and double-click
on Deploy database, as shown in Figure 2.
Figure 2. Deploying the pureScale database in PureApplication
- Once you double-click on Deploy database, you get new
windows to configure the database parameters. The list below describes
the fields that you need to complete, as shown in Figure 3:
- Database Name: Enter the database name. The database name must be less than eight characters, begin with an alphabetical character, and contain an underscore (_). It does not need other special characters (such as ?, !, *, or @).
- Description of Database: Your description of the database can be entered here, but is not required.
- Availability / Scalability: In this field, there are two options, standard and high. Select High for the pureScale database from PureData.
- Source field: You need to select Apply a default database workload standard. Once you select it, a default OLTP database is selected automatically, which is used for online transaction processing (OLTP). The database is optimized for transactional applications.
- Default user: Enter the user name. In the Password field, enter the password for the default user.
- Database size: Enter the size of the database. In this example, we use "20Gb".
- Database compatibility mode: The default compatibility mode is "DB2". You can choose the available database in the list, such as DB2 (default), Oracle, and so on.
- Database Version: You can select the version from the drop down list. We used "DB2 v10.1 for Linux". The version list is the database version and supported operating system platform, such as DB2 V10.1 for Linux.
- Database Level: You can select the database version and fix pack level with the supported operating system from the drop down list. We used "DB2 V10.1FixPack Level 2 for Linux".
- DB2 pureScale Instance: Select the DB2 pureScale existing instance name, which is already created on PureData.
- Schema file: This field is optional and you can browse for your schema file if you choose to use one.
Figure 3. Deploying pureScale database in the PureApplication dialog box
- Select Advanced Options to expand the field, and
from the drop-down list you can select the options for the following
- Pagesize: You can choose the page size for the dababase from the dropdown list. We used "4" as the page size.
- Code Set: Select the standard character code set. We used the "UTF-8" code set.
- Collating Sequence: You can select the standard collating sequence of the data source from the drop down list. We used "SYSTEM".
- Click OK when you have entered the information for all the required fields.
- After you click OK, the database deployment process is started. You
can see the status of the deployed database request, as shown in
Figure 4. Deploying pureScale database status in launching states
When the database instance status changes from "launching" to "running", the following information about the database instance is displayed, as shown in Figure 5:
- DB instance name
- DB instance IP address
- Port number
- Click on log to view the log. Figure 5 provides
the status of the database pattern creation.
When you click on log, you can check if there are any errors in the log and
check for information that pertains to the database pattern creation.
Figure 5. Database instance status
This article described how to integrate PureData System for Transactions with PureApplication System, which included how to register PureData with PureApplication and create a pureScale database pattern. These simple steps can help you to use the database from PureData for new or existing patterns of PureApplication.
- IBM PureData System for Transactions home page
- IBM PureSystems Centre
- IBM PureApplication System Information Center
- IBM Redbook: Adopting IBM PureApplication System V1.0
- IBM PureSystems resources on developerworks
Dig deeper into Cloud computing on developerWorks
Exclusive tools to build your next great app. Learn more.
Crazy about Cloud? Sign up for our monthly newsletter and the latest cloud news.
Deploy public cloud instances in as few as 5 minutes. Try the SoftLayer public cloud instance for one month.