You can troubleshoot common problems that you encounter when you deploy the patterns in
the IBM® SOA
Policy Gateway Pattern.
Failure to connect to external DataPower
appliance during deployment
Try the following solutions:
- Check with the DataPower® Administrator that the user
and password are valid:
- In the DataPower, Web GUI validate that the user
exists by going to .
- Check that the account exists.
- Check that user is privileged to use the XML Management Interface; for example, the system
administrator.
- The DataPower Administrator might have to check
whether the user account is enabled in the user agent settings; for example, the Basic
Authentication Settings.
- Check that the DataPower host name is correct
- Check that the DataPower XML Management Interface is
enabled.
Troubleshooting an error for the domain already existing
Try
the following solution:
- On the DataPower Control
Panel, open the Application Domains. Check if the Domain already exists.
Troubleshooting a port overlap error for the sample
application
If one of the sample services is unavailable, check
if the ports in your domain conflict with other domains.
Try the
following solutions:
- LOG in to DataPower and switch to the sample
domain. Then, open the Control Panel and click the XML Firewall icon. Check that the XML Firewalls
are all in Up state.
- Search for HTTP Front Side Handler. Check that the single HTTP
Front Side handler is in Up state.
Troubleshooting promotion failure
Many problems might arise during promotion,
including failure to connect to Governance Master during deployment.
Try the following solutions:
- Check the parameters:
- Check the user of the Governance Master WSRRCELL.
- Check the password for the user of the Governance Master WSRR Cell.
- Check the host name of the WSRR Governance Master Cell.
- Check the CELL name of the WSRR Governance Master Cell.
- Check the signer certificate exchange:
- Go to the Cell Default Trust Store of the Governance Master cell and make sure that there is a
certificate entry for the Dmgr or the Standalone server of the runtime environment.
- Go to each Runtime Environment and check the CellDefaultTrust store (for the ND environment
case) or the NodeDefaultTrustStore (for WSRR Standalone servers) to make sure that there is a
certificate for the Dmgr of the Governance Master.
- Export the LTPA keys from both cells by using the same password, and check that they are the
same (for example, the bytes).
- Make sure that the promotion properties file contains server sections with the appropriate host
and port, and user and password information. This information can be found in the ServiceRegistry
console for the Governance Master:
- Go to the GovernanceMasterDMgrHost or ServiceRegistry and switch to the Configurations
perspective. In the Actions section, find Promotion and open the promotion
properties file. For each environment, there should be XML elements for each server in the staging
WSRR node or cluster. If a production cluster or node exists, there should be server:port entries
for each, and in addition there should be user and password information.
- Check that the Service Version and SOAP Endpoint both have Classification for staging and
Production.
- In the Service Registry Console, select the SOA Governance perspective. Open the Service
Version, and select the Classifications tab. Staging and Production must be enabled.
Troubleshooting customized CLI failures
Try
the following solutions:
- Check the defaultLog for error messages in the DataPower Domain.
- Enable the CLI debugging and check those logs before any additional runs of the CLI.