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: docs/_posts/2016-02-26-sample-post-jekyll.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Sample post"
3
3
published: true
4
4
permalink: samplepost.html
5
5
summary: "This is some summary frontmatter for my sample post."
6
-
tags:[news, getting_started]
6
+
tags:
7
7
---
8
8
9
9
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
Copy file name to clipboardExpand all lines: docs/pages/cdp/cdp-Create-Zowe-CLI-profiles.md
+26-10Lines changed: 26 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,50 +10,62 @@ folder: cdp
10
10
11
11
### Step 1: Create a z/OSMF profile
12
12
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:
14
14
15
-
|Parameter| Description |
15
+
|Option| Description |
16
16
| --- | --- |
17
-
| host |Hostname of the z/OSMF server. |
17
+
| host |Host name of the z/OSMF server. |
18
18
| port | Port number of the z/OSMF server. |
19
19
| user | User ID to identify yourself to the z/OSMF server. |
20
20
| password | Password to identify yourself to the z/OSMF server. |
21
21
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).
To test the connection to the z/OSMF server using the profile:
37
+
31
38
```console
32
39
zowe zosmf check status
33
40
```
34
41
35
42
### Step 2: Create an SSH profile
36
43
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:
38
45
39
-
|Parameter| Description |
46
+
|Option| Description |
40
47
| --- | --- |
41
-
| host |Hostname of the SSH server. |
48
+
| host |Host name of the SSH server. |
42
49
| port | Port number of the SSH server. This will default to 22. |
43
50
| user | User ID to identify yourself to the SSH server. |
44
51
| password | Password to identify yourself to the SSH server. |
45
52
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).
This profile identifies the CICS environment for deployment. You need to know the following from your CICS system administrator:
64
76
65
-
|Parameter| Description |
77
+
|Option| Description |
66
78
| --- | --- |
67
79
| cicsplex | CPSM CICSplex name. |
68
80
| cicshlq | High Level Qualifier \(HLQ\) for the CICS data sets. |
69
81
| cpsmhlq | High Level Qualifier \(HLQ\) for the CPSM data sets. |
70
82
| 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. |
72
84
| 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. |
Copy file name to clipboardExpand all lines: docs/pages/cdp/cdp-Deploying-your-first-app.md
+39-11Lines changed: 39 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,31 +11,59 @@ toc: false
11
11
12
12
1. Install the Zowe CLI and cics-deploy plugin by following the steps in [Installation](cdp-Installation).
13
13
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).
15
15
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):
17
19
18
-
For example, to create a Node.js application using the Express Generator:
19
20
```console
20
21
npm install -g express-generator
21
22
express myExpressApp
22
23
cd myExpressApp
23
24
npm install
24
25
npm start
25
26
```
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.
27
27
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.
4. Package the Node.js application into a CICS bundle.
33
31
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.
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
+
40
67
### 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.
Copy file name to clipboardExpand all lines: docs/pages/cdp/cdp-Home.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
-
title: Home
2
+
title: Zowe CLI CICS deploy plugin
3
3
tags: [getting_started]
4
4
keywords:
5
5
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)."
6
6
sidebar: cdp_sidebar
7
-
permalink: cdp-Home.html
7
+
permalink: index.html
8
8
folder: cdp
9
9
---
10
10
@@ -13,7 +13,7 @@ It aims to provide an experience for developers and CI/CD automation pipelines s
13
13
The plug-in provides the following commands:
14
14
*[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.
15
15
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.
17
17
18
18
*[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.
Copy file name to clipboardExpand all lines: docs/pages/cdp/cdp-Installation.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,22 +10,26 @@ toc: false
10
10
---
11
11
12
12
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
+
13
14
```console
14
15
node --version
15
16
npm --version
16
17
```
17
18
18
19
2. Install [Zowe CLI](https://zowe.github.io/docs-site/latest/user-guide/cli-installcli.html). For example to install using npm:
20
+
19
21
```console
20
22
npm install -g zowe-cli
21
23
```
22
24
23
25
3. Install the cics-deploy plugin:
26
+
24
27
```console
25
28
zowe plugins install zowe-cli-cics-deploy-plugin
26
29
```
27
30
28
31
4. Verify the version of the plugin that is installed:
Copy file name to clipboardExpand all lines: docs/pages/cdp/cdp-Requirements.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,14 +10,17 @@ toc: false
10
10
---
11
11
12
12
### z/OS Management Facility
13
+
13
14
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.
14
15
15
16
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.
16
17
17
18
### z/OS Secure SHell daemon
19
+
18
20
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.
19
21
20
22
### DFHDPLOY utility
23
+
21
24
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.
22
25
23
26
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