Exporting a CICS bundle project to your local file system
If you do not have authorization to deploy a bundle directly to a z/OS® file system, or you want to back up your bundle source code, you can export the bundle project to your local file system.
Before you begin
- Set the file mode creation mask for the z/OS FTP daemon to ensure that the owner has write permissions. To configure this, use the UMASK statement in the FTP.DATA configuration file.
- Optionally, if you are also using UNIX System Services (USS) access control list (ACL) entries to control security, ensure that the default ACLs are inherited from the directory in zFS.
If your CICS bundle includes an OSGi Application Project (EBA) or an Enterprise Application Project (EAR), to develop and build the project, you must install the IBM® CICS® SDK for Java™ EE, Jakarta EE and Liberty, and the Liberty Developer Tools (LDT) if you are using CICS Explorer on Eclipse Marketplace. If you want to export the bundle without building it, you can add the built project to the root of your CICS bundle directly. Otherwise, you might receive a validation or exporting failure error. See Troubleshooting Liberty JVM servers and Java web applications.
About this task
Do not deploy the bundle project source to the z/OS UNIX file system from outside CICS Explorer because the tool packages the project for deployment and handles the file encoding for you.
Procedure
- In the Project Explorer view, right-click your CICS Bundle project and select Export.
The Export dialog opens.
- In the Export window, expand General, click Archive File, then click Next.
- Ensure that all the files in the project are selected. Enter a file name in the To archive file field. Ensure that Save in zip format is selected.
- Click Finish.
Results
What to do next
jar -xvf zipfile