You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This sample provides a Spring Boot application that uses the JCICS TSQ Java API to provide a RESTful CICS temporary storage queue (TSQ) browsing service. The sample demonstrates how to integrate Spring Boot with IBM CICS using the JCICS API on a CICS Liberty JVM server.
7
8
9
+
## Key Features
10
+
11
+
-**JCICS API Integration**: Direct use of CICS Java APIs for TSQ operations
12
+
-**RESTful Services**: Spring Boot REST endpoints for TSQ management
13
+
-**Multi-Module Project**: Separate application and CICS bundle modules
14
+
-**Multi-Build Support**: Compatible with both Gradle and Maven
15
+
-**CICS Bundle Deployment**: Automated deployment using CICS bundle plugins
16
+
17
+
## Table of Contents
18
+
19
+
-[Overview](#overview)
20
+
-[Key Features](#key-features)
21
+
-[Requirements](#requirements)
22
+
-[Downloading](#downloading)
23
+
-[Building the Sample](#building-the-sample)
24
+
-[Deploying to a CICS Liberty JVM server](#deploying-to-a-cics-liberty-jvm-server)
25
+
-[Running the Sample](#running-the-sample)
26
+
-[License](#license)
27
+
-[Additional Resources](#additional-resources)
28
+
-[Contributing](#contributing)
29
+
8
30
The sample is structured as a multi-module project with:
9
31
-**cics-java-liberty-springboot-jcics-app** - The Spring Boot application module
10
32
-**cics-java-liberty-springboot-jcics-cicsbundle** - The CICS bundle module for deployment
@@ -102,12 +124,12 @@ gradlew.bat clean build
102
124
103
125
Linux/Mac:
104
126
```bash
105
-
./mvnw clean package
127
+
./mvnw clean verify
106
128
```
107
129
108
130
Windows:
109
131
```cmd
110
-
mvnw.cmd clean package
132
+
mvnw.cmd clean verify
111
133
```
112
134
113
135
**Output:**
@@ -131,7 +153,7 @@ mvnw.cmd clean package
131
153
132
154
3.**Build the Project:**
133
155
- Right-click on root project → Run As → Gradle Build (or Maven Build)
134
-
- Goals: `clean build` (Gradle) or `clean package` (Maven)
156
+
- Goals: `clean build` (Gradle) or `clean verify` (Maven)
135
157
136
158
**Notes:**
137
159
- When building a WAR file for deployment to Liberty it is good practice to exclude Tomcat from the final runtime artifact. We demonstrate this in the pom.xml with the *provided* scope, and in build.gradle with the *providedRuntime()* dependency.
@@ -143,7 +165,7 @@ mvnw.cmd clean package
143
165
144
166
145
167
146
-
## Deploying to CICS
168
+
## Deploying to a CICS Liberty JVM server
147
169
148
170
### Prerequisites
149
171
@@ -153,7 +175,7 @@ Ensure you have the following features defined in your Liberty `server.xml`:
1. Copy the built WAR from your *target* or *build/libs* directory into an Eclipse CICS bundle project
218
+
1. Copy the built WAR from your *target* or *build/libs* directory into an Eclipse CICS Bundle Project
197
219
2. Create a new WAR bundlepart that references the WAR file
198
-
3. Deploy the CICS bundle project from CICS Explorer using the **Export Bundle Project to z/OS UNIX File System** wizard
220
+
3. Deploy the CICS Bundle Project from CICS Explorer using the **Export Bundle Project to z/OS UNIX File System** wizard
199
221
200
222
---
201
223
@@ -271,4 +293,15 @@ The example application is divided into four services which perform actions on a
271
293
272
294
273
295
## License
274
-
This project is licensed under [Eclipse Public License - v 2.0](LICENSE).
296
+
This project is licensed under [Eclipse Public License - v 2.0](LICENSE).
297
+
298
+
## Additional Resources
299
+
300
+
- [CICS TS for z/OS Documentation](https://www.ibm.com/docs/en/cics-ts)
301
+
- [Spring Boot Java applications for CICS, Part 1: JCICS, Gradle, and Maven](https://developer.ibm.com/tutorials/spring-boot-java-applications-for-cics-part-1-jcics-maven-gradle/)
Contributions are welcome! Please read our [contributing guidelines](https://github.com/cicsdev/.github/blob/main/CONTRIBUTING.md) for details on our code of conduct and the process for submitting pull requests.
0 commit comments