Skip to content

Commit 52781d9

Browse files
committed
readme build section update
1 parent 938eafc commit 52781d9

File tree

1 file changed

+19
-19
lines changed

1 file changed

+19
-19
lines changed

README.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -45,37 +45,37 @@ The VSAM examples use the sample file `SMPLXMPL`. For a sample CICS FILE definit
4545

4646
The sample can be built using the supplied Gradle or Maven build files to produce a WAR file and optionally a CICS Bundle archive.
4747

48-
#### Gradle (command line)
48+
### Building with Gradle
4949

50-
Run the following in a local command prompt:
50+
A WAR file is created inside the `build/libs` directory and a CICS bundle ZIP file inside the `build/distributions` directory.
5151

52-
`gradle clean build`
52+
If using the CICS bundle ZIP, the default CICS JVM server name `DFHWLP` should be modified using 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.
5353

54-
This creates a WAR file inside the `build/libs` directory and a CICS bundle ZIP file inside the `build/distributions` directory.
54+
| Tool | Command |
55+
| ----------- | ----------- |
56+
| Gradle Wrapper (Linux/Mac) | ```./gradlew clean build``` |
57+
| Gradle Wrapper (Windows) | ```gradle.bat clean build``` |
58+
| Gradle (command-line) | ```gradle clean build``` |
59+
| Gradle (command-line & setting jvmserver) | ```gradle clean build -Pcics.jvmserver=MYJVM``` |
5560

56-
If using the CICS bundle ZIP, the default CICS JVM server name `DFHWLP` should be modified using 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.
57-
58-
59-
`gradle clean build -Pcics.jvmserver=MYJVM`
60-
61-
62-
#### Maven (command line)
61+
### Building with Maven
6362

6463
First install the generated JAR file into a local Maven repository by running the following Maven command in a local command prompt
6564

6665
`mvn org.apache.maven.plugins:maven-install-plugin:3.1.3:install-file -Dfile=lib/cics-java-liberty-restappext-generated.jar -DgroupId=com.ibm.cicsdev -DartifactId=cics-java-liberty-restappext-generated -Dversion=1.0 -Dpackaging=jar -DlocalRepositoryPath=local-repo`
6766

68-
Next run the following in a local command prompt which will create a WAR file.
69-
70-
`mvn clean verify`
71-
72-
This creates a WAR file in the `target` directory.
73-
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 as follows.
67+
Next, run the appropriate Maven build command. This creates a WAR file in the `target` directory.
7568

76-
`mvn clean verify -Dcics.jvmserver=MYJVM`
69+
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.
7770

71+
| Tool | Command |
72+
| ----------- | ----------- |
73+
| Maven Wrapper (Linux/Mac) | ```./mvnw clean verify``` |
74+
| Maven Wrapper (Windows) | ```mvnw.cmd clean verify``` |
75+
| Maven (command-line) | ```mvn clean verify``` |
76+
| Maven (command-line & setting jvmserver) | ```mvn clean verify -Dcics.jvmserver=MYJVM``` |
7877

78+
## Deployment
7979
### To start a JVM server in CICS:
8080

8181
1. Define a Liberty JVM server called `DFHWLP` using the supplied sample definition `DFHWLP` in the CSD group `DFH$WLP`.

0 commit comments

Comments
 (0)