Merge pull request #143 from vera-chan/jvm-name-update

change default jvm server name to DFHWLP
IBM · Feb 27, 2020 · 555ae50 · 555ae50
2 parents 1d4c4ed + aed14fd
commit 555ae50
Show file tree

Hide file tree

Showing 4 changed files with 16 additions and 17 deletions.
diff --git a/README.md b/README.md
@@ -101,7 +101,7 @@ To create a CICS bundle in this way:
           <version>1.0.0</version>
           <extensions>true</extensions>
           <configuration>
-            <defaultjvmserver>JVMSRV1</defaultjvmserver>
+            <defaultjvmserver>DFHWLP</defaultjvmserver>
           </configuration>
         </plugin>
       </plugins>
@@ -136,7 +136,7 @@ To create a CICS bundle in this way:
               <goal>bundle-war</goal>
             </goals>
             <configuration>
-              <jvmserver>JVMSRV1</jvmserver>
+              <jvmserver>DFHWLP</jvmserver>
             </configuration>
           </execution>
         </executions>
@@ -170,7 +170,7 @@ The bundle directory of the BUNDLE definition should be set as follows: `<bundle
               <goal>deploy</goal>
             </goals>
             <configuration>
-              <defaultjvmserver>JVMSRV1</defaultjvmserver>
+              <defaultjvmserver>DFHWLP</defaultjvmserver>
               <url>http://yourcicsurl.com:9080</url>
               <username>${cics-user-id}</username>
               <password>${cics-password}</password>

diff --git a/samples/bundle-reactor-deploy/demo-bundle/pom.xml b/samples/bundle-reactor-deploy/demo-bundle/pom.xml
@@ -8,7 +8,7 @@
     <version>0.0.1-SNAPSHOT</version>
   </parent>
   <artifactId>demo-bundle</artifactId>
-  
+
   <!-- Tell Maven to build a CICS bundle -->
   <packaging>cics-bundle</packaging>
 
@@ -35,17 +35,17 @@
 
         <!-- Set the JVM server that the application will be installed into by default, This goes into the CICS bundle's manifest -->
         <configuration>
-          <defaultjvmserver>JVMSRV1</defaultjvmserver>
+          <defaultjvmserver>DFHWLP</defaultjvmserver>
         </configuration>
         <executions>
           <execution>
-          
+
             <!-- This declares that we want to run the deploy goal and we want this to happen during the verify phase of the lifecycle -->
             <goals>
               <goal>deploy</goal>
             </goals>
             <phase>verify</phase>
-            
+
             <!-- The below configuration is used to deploy the built bundle to CICS. -->
             <configuration>
               <!-- Set the transport, hostname, and port for your CMCI -->
@@ -68,4 +68,4 @@
 
     </plugins>
   </build>
-</project>
+</project>
diff --git a/samples/bundle-war-deploy/README.md b/samples/bundle-war-deploy/README.md
@@ -33,7 +33,7 @@ If you have an existing Java Maven project, add the snippet shown below to the p
       </goals>
       <configuration>
         <classifier>cics-bundle</classifier>
-        <jvmserver>JVMSRV1</jvmserver>
+        <jvmserver>DFHWLP</jvmserver>
         <url>http://yourcicsurl.com:9080</url>
         <username>${cics-user-id}</username>
         <password>${cics-password}</password>
@@ -55,6 +55,6 @@ To build all projects, install them into your local Maven repository, and deploy
 mvn clean install
 ```
 
-If you run into an `unable to find valid certification path to requested target` error, uncommenting the `<insecure>true</insecure>` line in the bundle's `pom.xml` is a quick fix but it poses security concerns by disabling TLS/SSL checking for certificates. For recommended solutions in real use, refer to [Troubleshooting](https://github.com/IBM/cics-bundle-maven#troubleshooting). 
+If you run into an `unable to find valid certification path to requested target` error, uncommenting the `<insecure>true</insecure>` line in the bundle's `pom.xml` is a quick fix but it poses security concerns by disabling TLS/SSL checking for certificates. For recommended solutions in real use, refer to [Troubleshooting](https://github.com/IBM/cics-bundle-maven#troubleshooting).
 
 If the build runs successfully, visit the servlet (http://yourcicsurl.com:9080/demo-war-0.0.1-SNAPSHOT if you used our sample as-is) to see what you published
diff --git a/samples/bundle-war-deploy/demo-war/pom.xml b/samples/bundle-war-deploy/demo-war/pom.xml
@@ -53,7 +53,7 @@
           <target>1.8</target>
         </configuration>
       </plugin>
-      
+
       <plugin>
         <groupId>com.ibm.cics</groupId>
         <artifactId>cics-bundle-maven-plugin</artifactId>
@@ -70,19 +70,19 @@
             <configuration>
               <!-- The bundle classifier indicates that the war should be packaged into a CICS bundle -->
               <classifier>cics-bundle</classifier>
-      
+
               <!-- Update the default JVM server that the application will be installed into by default, This is used when creating the bundle, and goes into the CICS bundle's manifest -->
-              <jvmserver>JVMSRV1</jvmserver>
-              
+              <jvmserver>DFHWLP</jvmserver>
+
               <!-- Set the transport, hostname, and port for your CMCI -->
               <url>http://localhost:9080</url>
               <!-- Uncomment the line below to disable ssl check for certificates-->
               <!--<insecure>true</insecure>-->
-              
+
               <!-- Use Maven's password encryption, or supply your credentials using environment variables or properties, as shown here. -->
               <username>${cics-user-id}</username>
               <password>${cics-password}</password>
-              
+
               <!-- Identify which bundle definition you're going to use from the CSD and which region and CICSplex you want to deploy to -->
               <bunddef>DEMOBUNDLE</bunddef>
               <csdgroup>BAR</csdgroup>
@@ -95,4 +95,3 @@
     </plugins>
   </build>
 </project>
-