Launch a client application

Program guide > (deprecated) Partitioning facility > An example of the partitioning facility > Run operations for the partitioning facility

Deprecated feature: The partitioning facility (WPF) feature is deprecated. You can configure partitioning with WebSphere eXtreme Scale.

Launch a client application

About this task

After you have balanced the partitions, you can run the client again. The output should reflect the balance operation:

IBM WAS, Release 5.1
J2EE Application Client Tool
Copyright IBM Corp., 1997-2003
WSCL0012I: Processing command line arguments.
WSCL0013I: Initializing the J2EE Application Client Environment.
WSCL0035I: Initialization of the J2EE Application Client Environment 
has completed.
WSCL0014I: Invoking the Application Client class 
com.ibm.websphere.wpf.client.WPFKeyBasedPartitionClient
Create Partitions from PK000001 to PK000010
1st call: PK000001->partiton=PK000001,server=NodeA/cluster_member_1
2nd call: PK000001->partiton=PK000001,server=NodeA/cluster_member_1
3rd call: PK000001->partiton=PK000001,server=NodeA/cluster_member_1
1st call: PK000002->partiton=PK000002,server=NodeA/cluster_member_3
2nd call: PK000002->partiton=PK000002,server=NodeA/cluster_member_3
3rd call: PK000002->partiton=PK000002,server=NodeA/cluster_member_3
1st call: PK000003->partiton=PK000003,server=NodeA/cluster_member_3
2nd call: PK000003->partiton=PK000003,server=NodeA/cluster_member_3
3rd call: PK000003->partiton=PK000003,server=NodeA/cluster_member_3
1st call: PK000004->partiton=PK000004,server=NodeA/cluster_member_3
2nd call: PK000004->partiton=PK000004,server=NodeA/cluster_member_3
3rd call: PK000004->partiton=PK000004,server=NodeA/cluster_member_3
1st call: PK000005->partiton=PK000005,server=NodeA/cluster_member_2
2nd call: PK000005->partiton=PK000005,server=NodeA/cluster_member_2
3rd call: PK000005->partiton=PK000005,server=NodeA/cluster_member_2
1st call: PK000006->partiton=PK000006,server=NodeA/cluster_member_2
2nd call: PK000006->partiton=PK000006,server=NodeA/cluster_member_2
3rd call: PK000006->partiton=PK000006,server=NodeA/cluster_member_2
1st call: PK000007->partiton=PK000007,server=NodeA/cluster_member_2
2nd call: PK000007->partiton=PK000007,server=NodeA/cluster_member_2
3rd call: PK000007->partiton=PK000007,server=NodeA/cluster_member_2
1st call: PK000008->partiton=PK000008,server=NodeA/cluster_member_1
2nd call: PK000008->partiton=PK000008,server=NodeA/cluster_member_1
3rd call: PK000008->partiton=PK000008,server=NodeA/cluster_member_1
1st call: PK000009->partiton=PK000009,server=NodeA/cluster_member_1
2nd call: PK000009->partiton=PK000009,server=NodeA/cluster_member_1
3rd call: PK000009->partiton=PK000009,server=NodeA/cluster_member_1
1st call: PK000010->partiton=PK000010,server=NodeA/cluster_member_1
2nd call: PK000010->partiton=PK000010,server=NodeA/cluster_member_1
3rd call: PK000010->partiton=PK000010,server=NodeA/cluster_member_1

Notice, the client calls have been dispatched to partitions that have been balanced to application server cluster_member2.

Another useful wpfadmin command is wpfadmin countActivePartitionsOnSevers:

wpfadmin countActivePartitionsOnSevers The result provides a count of the active partitions per cluster member:

WASX7209I: Connected to process "Deployment Manager" on node CellManager 
using SOAP connector;  The type of process is: DeploymentManager
WPFC0051I: Server Cell\NodeA\cluster_member_3: 3
WPFC0051I: Server Cell\NodeA\cluster_member_2: 3
WPFC0051I: Server Cell\NodeA\cluster_member_1: 4

Parent topic:

Run operations for the partitioning facility

Launch a client application

Parent topic:

Related tasks