-
Notifications
You must be signed in to change notification settings - Fork 51
Deploy Zowe in Sysplex
Download the most recent build from PR-2049 and install as usual.
Expected result: install the build and start Zowe as usual, the Zowe instance should pass all sanity test.
Run ${INSTANCE_DIR}/bin/utils/convert-to-zowe-yaml.sh
to convert your instance.env
to matching YAML configuration. The zowe.yaml
will be placed into your instance directory. Now you can remove your instance.env
and restart Zowe.
Expected result: Zowe should start without any issues.
When you customize zowe-setup-certificates.env
before running zowe-setup-certificates.sh
, you may already notice new variables COMPONENT_LEVEL_CERTIFICATES
, EXTERNAL_COMPONENT_CERTIFICATES
and EXTERNAL_COMPONENT_CERTIFICATE_ALIASES
. Follow the instruction, uncomment COMPONENT_LEVEL_CERTIFICATES
and run zowe-setup-certificates.sh
.
Expected result #1, you should see these extra files in <keystore>/localhost/
:
localhost.keystore.app-server.cer
localhost.keystore.app-server.cer-ebcdic
localhost.keystore.app-server.csr
localhost.keystore.app-server.key
localhost.keystore.app-server_signed.cer
localhost.keystore.gateway.cer
localhost.keystore.gateway.cer-ebcdic
localhost.keystore.gateway.csr
localhost.keystore.gateway.key
localhost.keystore.gateway_signed.cer
localhost.keystore.zss.cer
localhost.keystore.zss.cer-ebcdic
localhost.keystore.zss.csr
localhost.keystore.zss.key
localhost.keystore.zss_signed.cer
These are the PEM format certificates.
Expected result #2, run below command to list content of the keystore:
$ keytool -v -list -storepass password -storetype PKCS12 -keystore localhost.keystore.p12
You should see certificates generated for each components with proper alias name.
Expected result #3, check <keystore>/zowe-certificates.env
, it should show instructions like this:
# To configure certificate for gateway, you can add these entries to "components.gateway" of your YAML configuration:
# certificate:
# keystore:
# alias: gateway
# pem:
# key: /global/zowe/keystoretest/localhost/localhost.keystore-gateway.key
# certificate: /global/zowe/keystoretest/localhost/localhost.keystore-gateway.cer-ebcdic
# To configure certificate for app-server, you can add these entries to "components.app-server" of your YAML configuration:
# certificate:
# keystore:
# alias: app-server
# pem:
# key: /global/zowe/keystoretest/localhost/localhost.keystore-app-server.key
# certificate: /global/zowe/keystoretest/localhost/localhost.keystore-app-server.cer-ebcdic
# To configure certificate for zss, you can add these entries to "components.zss" of your YAML configuration:
# certificate:
# keystore:
# alias: zss
# pem:
# key: /global/zowe/keystoretest/localhost/localhost.keystore-zss.key
# certificate: /global/zowe/keystoretest/localhost/localhost.keystore-zss.cer-ebcdic
The component level certificate
instruction will overwrite part of the values defined in zowe.internalCertificate
.
- Configure zOSMF HA for Zowe in Sysplex
- Enable JWT function on zOSMF HA servers
- Enable single sign-on on zOSMF HA servers
- Enable Zowe to generate and evaluate PassTickets for APIML Services Zowe HA
- Deploy Zowe in Sysplex
- Test Zowe in Sysplex
- List of changes to the current documentation
- Additions to the current documentation