Developing dynamic scripting applications
To develop a dynamic scripting application, you use the CICS® Liberty development cycle. You develop your dynamic scripting application on your workstation, and then deploy it into your dynamic scripting CICS Liberty JVM server, by using the CICS Liberty development process.
About this task
Reviewing the artifacts that are delivered with the example application can help you to understand how all of the components fit together and are delivered. For more information about the example application, see Verifying the installation is successful.
Your application can contain both PHP and Java™ code. The feature pack encodes all log files in UTF-8 on z/OS® UNIX, and the PHP files are also expected to be encoded in UTF-8. The JCICS API uses the code page that is specified in the CICS region and not the underlying JVM.
Because the CICS TS Feature Pack for Dynamic Scripting V2.0 uses the CICS Liberty JVM server runtime environment, it supports all of the functions and interfaces to external products, for example Db2®, that the Liberty JVM supports. For more information about the CICS Liberty JVM server runtime environment, see JVM server runtime environment. For more information about configuring a JVM server to support Db2, see Configuring a JVM server to support Db2.
After your dynamic scripting application is deployed, you can enable tracing to debug both your PHP and your Java code.