Introduction
Based on SOA and implementing various industry-standard WebSphere Process Server (hereinafter called WPS), it is primarily used to automate business processes for people, workflows, applications, systems, platforms, and architectures. At present, more and more enterprise users choose to build integrated business system based on WPS, such as finance, communication and so on. They require high throughput and high availability of the system. In the actual planning and implementation, the use of cluster configuration and deployment is a common and effective way. This article describes how to install the WPS v6.1.2 product and the detailed steps for configuring the cluster based on the Informix v9.4 database under the UNIX environment (Aix,solaris or HP-UX).
The hardware and software required for the configuration of the WPS cluster are as follows:
2 operating systems for Aix,solaris or HP-UX UNIX hosts
WPS V6.1.2
Informix Dynamic Server 9.4 UC8
Informix JDBC Driver 3.00 JC3
The topological structure of WPS cluster
The WPS cluster (Cluster) provides application access to the user as a whole, and users do not need to focus on the specifics of the implementation at the bottom of the cluster.
This paper describes the configuration process of remote messaging and remote support cluster environment. This cluster environment is composed of three clusters, the specific topology is:
Application clusters provide both workload management and URL and EJB request failover capabilities for applications, as well as the BPC and HTM containers that provide support for applications that have long business processes and human business processes.
Remote messaging cluster, running the four-bus (SCA applications, SCA Systems, BPC, and CEI) provided by the WPS default provides an independent and efficient messaging engine.
Remote support clusters, deploying common event architectures and other applications such as business rule management, to provide asynchronous event queries.
The specific topology of this cluster pattern is shown in Figure 1.
Fig. 1 topological structure of the cluster environment
These three clusters are configured on different nodes of the two machines, that is, three of the members of the cluster are deployed on two machines. The two members in a cluster are identical copies of the cluster. Messaging engines, business support, and business process applications are located on separate clusters, so you can flexibly deploy the required resources based on the actual business load and hardware environment. This model, also known as Golden, is the most complex topology in WPS and is the first choice for most enterprise integrated application users, with the following advantages:
Reliability. Deploy all applications, messaging engines, and generic events to three clusters for easy management and use.
Scalability. Because the Messaging engine in the system is in a critical position, and there is likely to be an extension of subsequent access requirements, creating a separate Messaging Engine cluster can be easily implemented.
By separating the common event infrastructure (CEI) and the application, you can ensure that the two components do not compete with the same resources (memory and CPU) for issues such as the very large amount of processing that the system may encounter and its scalability. This topology can also help create a centralized event server to handle events from multiple sources.
All application servers are managed uniformly by Deployment manager, reducing the complexity of system management.
Pre-installation considerations
During the installation of the cluster environment, the information of the two hosts needs to be synchronized to ensure good communication between them. The main synchronization information includes the two host system time, time zone settings, and ensure that the difference between the two machines within 5 minutes, if the difference of more than 5 minutes, the joint operation will fail.
Update the Hosts file for both hosts (the default directory is/etc/hosts), ensuring that each machine contains each other's host name and corresponding IP address for mutual access between hosts.
When using the wizard to install and configure the profile, enter the configuration parameters in the order from top to bottom, and the change in the input order may cause an unknown error for WPS V6.12.
The steps of setting up the cluster environment
Informix Database Planning
WPS's cluster environment requires backing up the backend database. In order to improve the efficiency of the cluster in the actual operation, it is suggested that different databases be created according to the function. The details of the database are shown in the following table:
Table 1 Database specific information
Database name |
Description |
Wprcsdb |
Public database |
EVENT |
Common Event Architecture Database |
Ceidb |
Common event architecture Messaging Engine database |
Scasysdb |
Service component system Messaging Engine database |
Scaappdb |
Service component application Messaging Engine database |
Bpcdb |
Business Process Choreographer Database |
Bpcme |
Orchestration Orchestration Message Delivery Engine database |
Obsvrdb |
Business process choreographer Event collector database |
Note: This article selects the English Language database installation. If you are installing a database in a Chinese language, refer to the following: Adding a database language to the data source customization properties.