linkCells|linkCellsZOS Script

設定星狀拓蹼時，您可以使用 linkCells Script 來配置多個 Cell 之間的套版通訊。在 z/OS® 系統上，請改用 linkCellsZOS Script。

用途

使用 linkCells Script 來啟用智慧型管理 Cell 之間的通訊，這些 Cell 包含隨需應變路由器 (ODR) 所啟用的伺服器，可將工作要求遞送至其他管理 Cell。

在 z/OS 系統上，使用 linkCellsZOS Script。

位置

[AIX Solaris HP-UX Linux Windows] linkCells Script 位於 app_server_root/bin 目錄中。

[z/OS] linkCellsZOS Script 位於 app_server_root/bin 目錄中。

使用情形

從中心 Cell 執行 linkCells Script ，以將中心 Cell 與點 Cell 鏈結:

./linkCells.sh centerHost:center_cell_soap_port:user_id:password pointHost:point_cell_soap_port:user_id:password

從中心 Cell 執行 linkCellsZOS Script ，以將中心 Cell 與點 Cell 鏈結:

./linkCellsZOS.sh centerHost:center_cell_soap_port:user_id:password pointHost:point_cell_soap_port:user_id:password

範例

假設有一個實務範例，其中有兩個 Cell ，即 center 和 point1，且兩者都已啟用安全。對於中心 Cell ，部署管理程式的主機名稱是 centerHost， SOAP 埠是 8879，使用者名稱是 centerUID，密碼是 centerPWD。對於點 Cell ，部署管理程式的主機名稱是 point1Host， SOAP 埠是 8880，使用者名稱是 point1UID，密碼是 point1PWD。下列範例說明如何視需要將 center 和 point1 Cell 鏈結在一起，以支援星狀拓蹼。

./linkCells.sh centerHost:8879:centerUID:centerPWD point1Host:8880:point1UID:point1PWD

疑難排解

當您執行 linkCells Script 時，可能會顯示下列錯誤訊息。若要解決錯誤，請驗證 profile_home/properties/ssl.client.props 檔案中的 com.ibm.ssl.enableSignerExchangePrompt 內容是否設為 gui、 true或 stdin。透過設定此內容，用戶端可以從伺服器取得簽章者憑證，並因此與 Intelligent Management進行通訊。

當 com.ibm.ssl.enableSignerExchangePrompt 內容設為 gui 或 true時，會顯示簽章者交換視窗，且會要求您接受或拒絕憑證。如果您接受憑證，它會自動安裝在信任儲存庫中，且信號交換成功。如果您拒絕憑證，則它不會安裝在信任儲存庫中，且信號交換會失敗，因為憑證不受信任。

當 com.ibm.ssl.enableSignerExchangePrompt 內容設為 stdin時，會顯示簽章者交換 ASCII 提示，且會要求您接受或拒絕憑證。如果您接受憑證，它會自動安裝在信任儲存庫中，且信號交換成功。如果您拒絕憑證，則它不會安裝在信任儲存庫中，且信號交換會失敗，因為憑證不受信任。

$ ./linkCells.sh centerHost:center_cell_soap_port:user_id:password pointHost:point_cell_soap_port:user_id:password

"Begin linking cells..."

WASX7209I: Connected to process "dmgr" on node dmgr using SOAP connector. The type of process is: DeploymentManager

CWPKI0022E: SSL HANDSHAKE FAILURE:  A signer with SubjectDN "CN=edgeaphid16.rtp.raleigh.ibm.com, OU=e16VEcell, 
OU=edgeaphid16CellManager02, O=IBM, C=US" was sent from target host:port "9.42.96.77:8915".
The signer may need to be added to local trust store "c:/AutoWAS2/09072011/WAS/profiles/node1/etc/trust.p12" 
located in SSL configuration alias "DefaultSSLSettings" loaded from SSL configuration file 
"file:c:\AutoWAS2\09072011\WAS\profiles\node1/properties/ssl.client.props".
The extended error message from the SSL handshake exception is:
"PKIX path building failed: 
java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.;
internal cause is: 
java.security.cert.CertPathValidatorException: The certificate issued by CN=edgeaphid16.rtp.raleigh.ibm.com, 
OU=Root Certificate, OU=e16VEcell, OU=edgeaphid16CellManager02, O=IBM, C=US is not trusted;
internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error".

CWPKI0040I: An SSL handshake failure occurred from a secure client.  The server's SSL signer has to be added to the 
client's trust store. A retrieveSigners utility is provided to download signers from
the server but requires administrative permission. Check with your administrator to have this utility run to setup 
the secure environment before running the client. 
Alternatively, the com.ibm.ssl.enableSignerExchangePrompt can be enabled in ssl.client.props for "DefaultSSLSettings" 
in order to allow acceptance of the signer during the connection attempt.

WASX7023E: Error creating "SOAP" connection to host "edgeaphid16.rtp.raleigh.ibm.com"; 
exception information:
com.ibm.websphere.management.exception.ConnectorNotAvailableException: 
[SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: 
javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: 
PKIX path building failed:
java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.;
internal cause is:
java.security.cert.CertPathValidatorException: The certificate issued by CN=edgeaphid16.rtp.raleigh.ibm.com, 
OU=Root Certificate, OU=e16VEcell, OU=edgeaphid16CellManager02,
O=IBM, C=US is not trusted;
internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error;
targetException=java.lang.IllegalArgumentException: Error opening socket: javax.net.ssl.SSLHandshakeException: 
com.ibm.jsse2.util.g: PKIX path building failed:
java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.;
internal cause is:
java.security.cert.CertPathValidatorException: The certificate issued by CN=edgeaphid16.rtp.raleigh.ibm.com, 
OU=Root Certificate, OU=e16VEcell, OU=edgeaphid16CellManager02,
O=IBM, C=US is not trusted; internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error]

WASX7213I: This scripting client is not connected to a server process; please refer to the log file 
c:\AutoWAS2\09072011\WAS\profiles\node1\logs\wsadmin.traceout for additional information.