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
The `cics-deploy push bundle` command pushes a bundle from the working directory to a target CICS environment. It requires the use of a zosmf profile and an ssh profile, use of a cics-deploy profile is also encouraged (for more information on these dependencies see [Requirements for Push](#push_req)). You can request assistance on using the push command by issuing the following command:
198
+
The `cics-deploy push bundle` command pushes a bundle from the working directory to a target CICS environment. It requires the use of a zosmf profile and an ssh profile in order to do so, use of a cics-deploy profile is also encouraged (for more information on these dependencies see [Requirements for Push](#push_req)). You can request assistance on using the push command by issuing the following command:
199
199
200
200
`zowe cics-deploy push bundle --help`
201
201
202
-
If you have configured default profiles for zosmf, ssh and cics-deploy then two further items are needed:
202
+
If you have configured default profiles for zosmf, ssh and cics-deploy then only two further items are needed:
203
203
204
204
1. An up to 8 character unique name to use for the Bundle resource in CICS.
205
205
2. A directory in the target zFS in which do stage the Bundle's resources.
@@ -208,7 +208,7 @@ For example, you might issue the following command:
This command will cause cics-deploy to attempt to deploy a bundle from the working directory to the target CICS environment under the name `EXAMPLE1`. If a Bundle already exists in the target environment with the same name, cics-deploy will return an error. You may instruct cics-deploy to overwrite the existing Bundle by adding the --overwrite parameter, for example:
211
+
This command will cause cics-deploy to attempt to deploy a bundle from the current working directory to the target CICS environment under the name `EXAMPLE1`. If a Bundle already exists in the target environment with the same name, cics-deploy will return an error. You may instruct cics-deploy to overwrite the existing Bundle by adding the --overwrite parameter, for example:
@@ -224,10 +224,10 @@ The `cics-deploy push bundle` command consists of several separate actions, each
224
224
225
225
1. It undeploys an existing Bundle using `zowe cics-deploy undeploy bundle` (See [Undeploying a CICS Bundle](#undeploying)).
226
226
2. It uploads the local Bundle directory to zFS using `zowe zos-files upload dir-to-uss`.
227
-
3. If the bundle contains a package.json file it runs `npm install` using `zowe zos-uss issue ssh`.
228
-
4. It deploys an Bundle using `zowe cics-deploy deploy bundle` (See [Deploying a CICS Bundle](#deploying)).
227
+
3. If the bundle contains a package.json file it runs `npm install`on the remote system using `zowe zos-uss issue ssh`.
228
+
4. It deploys a Bundle using `zowe cics-deploy deploy bundle` (See [Deploying a CICS Bundle](#deploying)).
229
229
230
-
Advanced users may prefer to use these sub-commands themselves. For example, if the target CICS regions are not CPSM managed then you might use Zowe to generate and subsequently upload the Bundle, and your own scripts to deploy the Bundle into a CICS region.
230
+
Advanced users may prefer to use these sub-commands in preference to the `push` command. For example, if the target CICS regions are not CPSM managed then you might use Zowe to generate and subsequently upload the Bundle, and your own scripts to deploy the Bundle into a CICS region.
0 commit comments