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
Copy file name to clipboardExpand all lines: README.md
+23-24Lines changed: 23 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,38 +50,37 @@ a CICS bundle project.
50
50
1. Ensure the web project is targeted to compile at a level that is compatible with the Java level being used on CICS. This can be achieved by editing the Java Project Facet in the project properties.
51
51
1. Create a CICS bundle project called `com.ibm.cicsdev.restapp.cicsbundle` and add a dynamic web project include for the project created in step 1.
52
52
53
-
###Building the Example
53
+
## Building the Sample
54
54
55
-
The sample can be built using the supplied Gradle or Maven build files to produce a WAR file and optionally a CICS Bundle archive.
55
+
The sample can be built using Gradle or Maven to produce a WAR file and optionally a CICS Bundle archive.
56
56
57
-
#### Gradle (command line)
57
+
###Building with Gradle
58
58
59
-
Run the following in a local command prompt:
59
+
A WAR file is created inside the `build/libs` directory and a CICS bundle ZIP file inside the `build/distributions` directory.
60
60
61
-
`gradle clean build`
61
+
If using the CICS bundle ZIP, the CICS JVM server name should be modified in the `cics.jvmserver` property in the gradle build [file](build.gradle) to match the required CICS JVMSERVER resource name, or alternatively can be set on the command line.
62
62
63
-
This creates a WAR file inside the `build/libs` directory and a CICS bundle ZIP file inside the `build/distributions` directory.
If using the CICS bundle ZIP, the CICS JVM server name should be modified in the `cics.jvmserver` property in the gradle build [file](build.gradle) to match the required CICS JVMSERVER resource name, or alternatively can be set on the command line as follows.
66
70
71
+
### Building with Apache Maven
72
+
A WAR file and a CICS bundle ZIP file are created inside the `target/` directory.
67
73
68
-
`gradle clean build -Pcics.jvmserver=MYJVM`
69
-
70
-
71
-
#### Maven (command line)
72
-
73
-
Run the following in a local command prompt which will create a WAR file for deployment.
74
-
75
-
`mvn clean verify`
76
-
77
-
This creates a WAR file in the `target` directory.
78
-
79
-
If building a CICS bundle ZIP the CICS bundle plugin bundle-war goal is driven using the maven verify phase. The CICS JVM server name should be modified in the `<cics.jvmserver>` property in the [`pom.xml`](pom.xml) to match the required CICS JVMSERVER resource name, or alternatively can be set on the command line as follows.
80
-
81
-
`mvn clean verify -Dcics.jvmserver=MYJVM`
82
-
74
+
If building a CICS bundle ZIP the CICS bundle plugin bundle-war goal is driven using the maven verify phase. The CICS JVM server name should be modified in the `<cics.jvmserver>` property in the [`pom.xml`](pom.xml) to match the required CICS JVMSERVER resource name, or alternatively can be set on the command line.
1. Enable Java support in the CICS region by adding the `SDFJAUTH` library to the `STEPLIB` concatenation and setting `USSHOME` and the `JVMPROFILEDIR` SIT parameters.
87
86
* This step is **not** required if using CICS 5.5 or later
@@ -101,9 +100,9 @@ If building a CICS bundle ZIP the CICS bundle plugin bundle-war goal is driven u
101
100
**Note:** A sample DFHCSDUP input file for the required CICS BUNDLE resource definition is supplied in the supporting file [DFHCSD.txt](etc/DFHCSD.txt) file.
102
101
103
102
104
-
###Running the Example
103
+
## Running the Sample
105
104
106
-
####Using a web browser you can issue the following HTTP GET requests
105
+
### Using a web browser you can issue the following HTTP GET requests
0 commit comments