Skip to content

Commit ff6e641

Browse files
authored
Merge branch 'master' into fix/overwrite
2 parents 33ef007 + 738cb76 commit ff6e641

8 files changed

+132
-49
lines changed

docs/_posts/2016-02-26-sample-post-jekyll.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Sample post"
33
published: true
44
permalink: samplepost.html
55
summary: "This is some summary frontmatter for my sample post."
6-
tags: [news, getting_started]
6+
tags:
77
---
88

99
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries

docs/index.md

Lines changed: 0 additions & 20 deletions
This file was deleted.

docs/pages/cdp/cdp-Create-Zowe-CLI-profiles.md

Lines changed: 26 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -10,50 +10,62 @@ folder: cdp
1010

1111
### Step 1: Create a z/OSMF profile
1212

13-
This profile identifies the z/OSMF server that has access to the directory on z/OS into which the CICS bundle will be deployed. You need to know the following from your z/OS system administrator:
13+
This profile defines the parameters needed to connect to the z/OSMF server on z/OS. You need to know the following from your z/OS system administrator:
1414

15-
| Parameter | Description |
15+
| Option | Description |
1616
| --- | --- |
17-
| host | Hostname of the z/OSMF server. |
17+
| host | Host name of the z/OSMF server. |
1818
| port | Port number of the z/OSMF server. |
1919
| user | User ID to identify yourself to the z/OSMF server. |
2020
| password | Password to identify yourself to the z/OSMF server. |
2121

22+
**Note**: The user ID needs to have sufficient permissions to remove and create directories and files in the directory specified by `--targetdir` in the cics-deploy profile. The user ID also needs permission to submit JCL and to run the DFHDPLOY utility as described in the **Security** heading in topic [Automate the deployment and undeployment of CICS bundles and applications with the DFHDPLOY utility](https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/applications/deploying/dfhdploy_overview.html).
23+
2224
For example, to create a z/OSMF profile:
25+
2326
```console
2427
zowe profiles create zosmf-profile myzos --host myzos.example.com --port 3000 --user myuserid --password mypassword --reject-unauthorized false --overwrite
2528
```
29+
2630
For help on using the options:
31+
2732
```console
2833
zowe profiles create zosmf-profile --help
2934
```
35+
3036
To test the connection to the z/OSMF server using the profile:
37+
3138
```console
3239
zowe zosmf check status
3340
```
3441

3542
### Step 2: Create an SSH profile
3643

37-
This profile defines the parameters needed to connect. to the remote SSH server. You need to know the following from your z/OS system administrator:
44+
This profile defines the parameters needed to connect to the SSH server on z/OS. You need to know the following from your z/OS system administrator:
3845

39-
| Parameter | Description |
46+
| Option | Description |
4047
| --- | --- |
41-
| host | Hostname of the SSH server. |
48+
| host | Host name of the SSH server. |
4249
| port | Port number of the SSH server. This will default to 22. |
4350
| user | User ID to identify yourself to the SSH server. |
4451
| password | Password to identify yourself to the SSH server. |
4552

46-
It is recommended that you use the same user ID and host to connect with SSH as is used in the z/OSMF profile, failure to do so results in undefined behaviour.
53+
**Note**: It is recommended that you use the same user ID and host name to connect with SSH as is used in the z/OSMF profile, failure to do so results in undefined behaviour. When an SSH connection is made, the user's remote [z/OS shell .profile](https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxa400/cupro.htm) is used to set-up the shell environment and variables. This remote .profile should include any necessary environment variables and npm configuration required to run `npm install`. This is descibed in [Installing and configuring](https://www.ibm.com/support/knowledgecenter/SSTRRS_6.0.0/com.ibm.nodejs.zos.v6.doc/install.htm).
4754

4855
For example, to create an SSH profile:
56+
4957
```console
5058
zowe profiles create ssh-profile myzos --host myzos.example.com --user myuserid --password mypassword --overwrite
5159
```
60+
5261
For help on using the options:
62+
5363
```console
5464
zowe profiles create ssh-profile --help
5565
```
66+
5667
To test the connection to the SSH server using the profile:
68+
5769
```console
5870
zowe zos-uss issue ssh 'uname -a'
5971
```
@@ -62,23 +74,27 @@ zowe zos-uss issue ssh 'uname -a'
6274

6375
This profile identifies the CICS environment for deployment. You need to know the following from your CICS system administrator:
6476

65-
| Parameter | Description |
77+
| Option | Description |
6678
| --- | --- |
6779
| cicsplex | CPSM CICSplex name. |
6880
| cicshlq | High Level Qualifier \(HLQ\) for the CICS data sets. |
6981
| cpsmhlq | High Level Qualifier \(HLQ\) for the CPSM data sets. |
7082
| scope | CPSM scope to identify the CICS region or group of regions to deploy your application. |
71-
| csdgroup | CICS CSD group name or CPSM BAS resource group name into which the bundle is defined. If not specified, BUNDLE resources are defined in CPSM BAS for installation and then removed. |
83+
| resgroup or basgroup | CICS CSD group name or BAS resource group name into which the bundle is defined. If not specified, BUNDLE resources are defined in CPSM BAS for installation and then removed. |
7284
| jobcard | JCL jobcard to use when submitting JCL that will run the CICS utility DFHDPLOY. If not specified, a default jobcard will be used. |
73-
| targetdir | Target zFS location to which CICS bundles should be uploaded. |
85+
| targetdir | Target directory on z/OS to which CICS bundles should be uploaded. |
7486

7587
For example to create a cics-deploy profile:
88+
7689
```console
7790
zowe profiles create cics-deploy-profile example --cicsplex PLEX1 --cicshlq CICSTS55.CICS720 --cpsmhlq CICSTS55.CPSM550 --scope TESTGRP1 --csdgroup BUNDGRP1 --targetdir /var/cicsts/bundles
7891
--overwrite
7992
```
93+
8094
For help on using the options:
95+
8196
```console
8297
zowe profiles create cics-deploy-profile --help
8398
```
99+
84100
To test the cics-deploy profile, follow the steps in [Deploying your first app](cdp-Deploying-your-first-app).

docs/pages/cdp/cdp-Deploying-your-first-app.md

Lines changed: 39 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -11,31 +11,59 @@ toc: false
1111

1212
1. Install the Zowe CLI and cics-deploy plugin by following the steps in [Installation](cdp-Installation).
1313

14-
1. Create Zowe CLI profiles for z/OSMF, SSH, and cics-deploy by following the steps in [Create Zowe CLI profiles](cdp-Create-Zowe-CLI-profiles).
14+
2. Create Zowe CLI profiles for z/OSMF, SSH, and cics-deploy by following the steps in [Create Zowe CLI profiles](cdp-Create-Zowe-CLI-profiles).
1515

16-
1. Create a Node.js application.
16+
3. Create a Node.js application.
17+
18+
For example, to create a Node.js application using the [Express Application Generator](https://expressjs.com/en/starter/generator.html):
1719

18-
For example, to create a Node.js application using the Express Generator:
1920
```console
2021
npm install -g express-generator
2122
express myExpressApp
2223
cd myExpressApp
2324
npm install
2425
npm start
2526
```
26-
The Node.js web server will start and you can browse to [http://localhost:3000](http://localhost:3000) to see the running application. Use CTRL+C to stop the Node.js web server.
2727

28-
1. Package the Node.js application into a CICS bundle. The port needs to be available for use by the CICS region on z/OS.
28+
The Node.js application will start. You can call the application from a browser using URL [http://localhost:3000/](http://localhost:3000/), and press CTRL+C to stop it.
2929

30-
```console
31-
zowe cics-deploy generate bundle --startscript app.js --port 3000 --overwrite
32-
```
30+
4. Package the Node.js application into a CICS bundle.
3331

34-
1. Deploy the CICS bundle into CICS. Replace the value for `--targetdir` with a directory on z/OS that your user ID has write access to, and the CICS region user ID has read access to.
32+
Make sure you are in the root directory of the application. Replace the value for `--port` with one that is available for use by the CICS region on z/OS.
3533

3634
```console
37-
zowe cics-deploy push bundle --name Express --targetdir /u/userid/bundles --overwrite
35+
zowe cics-deploy generate bundle --port 3000 --overwrite
3836
```
3937

38+
The output will show the directories and files created to form a CICS bundle:
39+
40+
```console
41+
define : NODEJSAPP "myexpressapp" with startscript "./bin/www"
42+
create : nodejsapps
43+
create : nodejsapps/myexpressapp.nodejsapp
44+
create : nodejsapps/myexpressapp.profile
45+
create : .zosattributes
46+
create : META-INF
47+
create : META-INF/cics.xml
48+
CICS Bundle generated with bundleid "myexpressapp"
49+
```
50+
51+
5. Deploy the CICS bundle into CICS.
52+
53+
Replace the value for `--name` with the name of the BUNDLE resource to be created in CICS.
54+
55+
```console
56+
zowe cics-deploy push bundle --name Express --overwrite
57+
```
58+
59+
A progress bar is shown and updated as the CICS bundle is deployed and the application is started. This can take a few minutes. If there are errors, retry with the `--verbose` option for more detailed output.
60+
61+
6. Test the Node.js application.
62+
63+
You can call the application from a browser using URL [http://myzos:3000/](http://myzos:3000/), replacing _myzos_ with the host name of the z/OS system, and _3000_ with the port specified in step 4.
64+
65+
You can make changes to the application and redeploy it by repeating step 5.
66+
4067
### Results
41-
The Node.js web server will start and you can browse to [http://myzos:3000](http://myzos:3000) to see the running application.
68+
69+
The Node.js application is packaged into a CICS bundle on the workstation, uploaded to a directory on z/OS, and is running in CICS.

docs/pages/cdp/cdp-Home.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Home
2+
title: Zowe CLI CICS deploy plugin
33
tags: [getting_started]
44
keywords:
55
summary: "The Zowe command line interface (CLI) provides a simple and streamlined way to interact with IBM z/OS. The cics-deploy plugin extends the Zowe CLI to deploy applications developed on a workstation to IBM CICS Transaction Server for z/OS (CICS)."
66
sidebar: cdp_sidebar
7-
permalink: cdp-Home.html
7+
permalink: index.html
88
folder: cdp
99
---
1010

@@ -13,7 +13,7 @@ It aims to provide an experience for developers and CI/CD automation pipelines s
1313
The plug-in provides the following commands:
1414
* [zowe cics-deploy generate bundle]({{ site.path_to_generated_docs }}CLIReadme.md#module-generate) - Generate a CICS bundle in the working directory. Typically used by developers to package their existing application as a CICS bundle.
1515

16-
* [zowe cics-deploy push bundle]({{ site.path_to_generated_docs }}CLIReadme.md#module-push) - Firstly undeploy the previous version of the CICS bundle from CICS incase it was been previously deployed. Then copy the bundle from the working directory to a z/OS directory, and run npm to install dependencies for each Node.js application in the bundle. Finally deploy the bundle to one or more CICS regions within a CICSplex. Typically used by developers to deploy applications in CICS ready for testing.
16+
* [zowe cics-deploy push bundle]({{ site.path_to_generated_docs }}CLIReadme.md#module-push) - Firstly undeploy the previous version of the CICS bundle from CICS incase it had been previously deployed. Then copy the bundle from the working directory to a z/OS directory, and run npm to install dependencies for each Node.js application in the bundle. Finally deploy the bundle to one or more CICS regions within a CICSplex. Typically used by developers to deploy applications in CICS ready for testing.
1717

1818
* [zowe cics-deploy deploy bundle]({{ site.path_to_generated_docs }}CLIReadme.md#module-deploy) - Deploy a CICS bundle that is in a z/OS directory to one more CICS regions within a CICSplex. The DFHDPLOY utility is used to define the BUNDLE resource in a CICS system definition (CSD) file or CPSM Business Application Services (BAS) file, then install and enable the resource in the target CICS regions. Typically used by developers and CI-CD pipelines that require more precise control when deploying applications to CICS, for example to install the bundle in subsets of CICS regions in a cluster in a manner that maintains the availability of the application for clients.
1919

docs/pages/cdp/cdp-Installation.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,22 +10,26 @@ toc: false
1010
---
1111

1212
1. Install [Node.js V8.0](https://nodejs.org/en/download/) or later, and Node Package Manager (npm) V5.0 or later, that are required by Zowe CLI. To verify the versions installed:
13+
1314
```console
1415
node --version
1516
npm --version
1617
```
1718

1819
2. Install [Zowe CLI](https://zowe.github.io/docs-site/latest/user-guide/cli-installcli.html). For example to install using npm:
20+
1921
```console
2022
npm install -g zowe-cli
2123
```
2224

2325
3. Install the cics-deploy plugin:
26+
2427
```console
2528
zowe plugins install zowe-cli-cics-deploy-plugin
2629
```
2730

2831
4. Verify the version of the plugin that is installed:
32+
2933
```console
3034
zowe plugins list
3135
```

docs/pages/cdp/cdp-Requirements.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,17 @@ toc: false
1010
---
1111

1212
### z/OS Management Facility
13+
1314
A [z/OS Management Facility (z/OSMF)](https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.izua300/IZUHPINFO_PartConfiguring.htm) server is required to run the [push bundle](Commands#command-push-bundle), [deploy bundle](Commands#command-deploy-bundle), and [undeploy bundle](Commands#command-undeploy-bundle) commands. These commands call the API for [`zowe zos-jobs submit`](https://zowe.github.io/docs-site/latest/user-guide/cli-usingcli.html#zos-jobs) to submit JCL that executes the DFHDPLOY utility to deploy and undeploy CICS bundles.
1415

1516
The z/OSMF server is also required by the [push bundle](Commands#command-push-bundle) command when it uses the API for [`zowe files upload dir-to-uss`](https://github.com/zowe/zowe-cli/issues/207) to copy a CICS bundle to a z/OS directory.
1617

1718
### z/OS Secure SHell daemon
19+
1820
The [z/OS Secure SHell daemon (sshd)](https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.foto100/sshset.htm) is required to run the [push bundle](Commands#command-push-bundle) command. This command uses the API for [`zowe zos-uss issue ssh`](https://github.com/zowe/zowe-cli/pull/308) to remove old files from the CICS bundle directory on z/OS and execute `npm install` on z/OS to install dependencies for Node.js applications.
1921

2022
### DFHDPLOY utility
23+
2124
The [DFHDPLOY](https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/applications/deploying/dfhdploy_overview.html) utility is provided with IBM CICS Transaction Server (CICS) and is required to run the [push bundle](Commands#command-push-bundle), [deploy bundle](Commands#command-deploy-bundle), and [undeploy bundle](Commands#command-undeploy-bundle) commands. These commands start DFHDPLOY with a script to perform deploy and undeploy operations. For example the deploy operation will define, install, then enable a CICS BUNDLE resource in a one or more CICS regions.
2225

2326
The DFHDPLOY utility requires CICSPlex System Manager \(CPSM\) that is also provided with CICS to be configured, and for CPSM to be connected to the target CICS regions.

0 commit comments

Comments
 (0)