Troubleshooting dynamic scripting applications
If you have problems with your dynamic scripting application, you can use troubleshooting steps to help you identify the problem. The problem might be in the configuration, deployment, or at run time.
About this task
If you have problems with your application, use the following troubleshooting steps:
Procedure
- Check that you have the correct versions of software and service installed. For more information, see Prerequisites.
- Check that you can successfully run the example application, as described in Verifying the installation is successful.
- Check that your dynamic scripting application is successfully deployed to the correct CICS region.
- Check that your application does not contravene any of the restrictions that are listed in Restrictions.
- If your application is migrated from a previous version of the Dynamic Scripting Feature Pack, check that you comply with all of the items that are mentioned in Migrating applications from version 1.x to version 2.0.
- If you want to see which php.ini file that your application loaded, you can issue phpinfo() in your PHP script and find the information from the "Loaded Configuration File" row. A "default" prefix means the php.ini is loaded from the PHP engine, while a "user" prefix means the php.ini is loaded from a user OSGi bundle.
- Follow the procedure in Troubleshooting Liberty JVM servers and Java web applications and verify whether any of the conditions apply.