WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Launching a client application

About this task

To test the server, launch the Java 2 Platform Enterprise Edition (J2EE) launchclient application.

Type the following in the command window:
launchclient [WAS_HOME]\profiles\[APP_SERVER_PROFILE]\installedApps\Cell\ 
WPFKeyBasedPartitionSample.ear -CCproviderURL=corbaloc::<host>:<port>

<host> - hostname where the application server runs

<port> - BOOTSTRAP_ADDRESS

To find the port: In the administrative console, click Servers > Application Servers > server_name > Communications > Ports. Then, find the port value of the BOOTSTRAP_ADDRESS.

The result should look similar to the following:
IBM WebSphere Application Server, 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_1
2nd call: PK000005->partiton=PK000005,server=NodeA/cluster_member_1
3rd call: PK000005->partiton=PK000005,server=NodeA/cluster_member_1
1st call: PK000006->partiton=PK000006,server=NodeA/cluster_member_1
2nd call: PK000006->partiton=PK000006,server=NodeA/cluster_member_1
3rd call: PK000006->partiton=PK000006,server=NodeA/cluster_member_1
1st call: PK000007->partiton=PK000007,server=NodeA/cluster_member_1
2nd call: PK000007->partiton=PK000007,server=NodeA/cluster_member_1
3rd call: PK000007->partiton=PK000007,server=NodeA/cluster_member_1
1st call: PK000008->partiton=PK000008,server=NodeA/cluster_member_3
2nd call: PK000008->partiton=PK000008,server=NodeA/cluster_member_3
3rd call: PK000008->partiton=PK000008,server=NodeA/cluster_member_3
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_3
2nd call: PK000010->partiton=PK000010,server=NodeA/cluster_member_3
3rd call: PK000010->partiton=PK000010,server=NodeA/cluster_member_3

Compare the results to the wpfadmin listActive command executed in previous section, the application server where the request executed is where it had been activated.

Note: If the particular partition targeted method call is routed to a different partition, the application was probably redeployed either during the application installation or prior to you trying this ear. See the wpfstubutil command in the programming guide for instructions to repair the example ear.



Related tasks
Running operations for the partitioning facility
Related reference
Troubleshooting launchclient
Task topic    

Terms of Use | Feedback

Last updated: Nov 30, 2007 4:03:08 PM EST
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/WPF51/twpflaunchclient.html