Para testar o servidor, ative o aplicativo launchclient J2EE (Java 2 Platform Enterprise Edition).
launchclient [WAS_HOME]\profiles\[APP_SERVER_PROFILE]\installedApps\Cell\
WPFKeyBasedPartitionSample.ear -CCproviderURL=corbaloc::
<host>:<porta>
<host> - nome do host no qual o servidor de aplicativos é executado
<porta> - BOOTSTRAP_ADDRESS
Para localizar a porta: No console administrativo, clique em Servidores > Servidores de Aplicativos > server_name > Comunicações > Portas.
Em seguida, localize o valor da porta do BOOTSTRAP_ADDRESS.
O resultado deve ser semelhante ao seguinte:
IBM WebSphere Application Server, Release 5.1 J2EE Application Client Tool Copyright IBM Corp., 1997-2003 WSCL0012I: Processando argumentos da linha de comandos. WSCL0013I: Inicializando o J2EE Application Client Environment. WSCL0035I: A inicialização do J2EE Application Client Environment foi concluída. WSCL0014I: Chamando a classe do Application Client com.ibm.websphere.wpf.client.WPFKeyBasedPartitionClient Criar Partições de PK000001 a 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 os resultados com o comando wpfadmin listActive executado na seção anterior, o servidor de aplicativos no qual o pedido foi executado é o local em que ele foi ativado.
Related tasks
Executando Operações para o Recurso de Particionamento
Related reference
Resolução de Problemas do launchclient