Need help to have an operational Zowe main server

[Jem11111]

Hello,

Can you help me to fix the problems to have an operational Zowe main server ?
I send to you my yaml file and the output of Zowe main server.

Thanks,

Regards.

Jean-Marc Mirande-Ney

[Jem11111]

SysoutJem.pdf
Yamljem.pdf

[JoeNemo]

There are messages in your log config problems. Maybe an issue near this part of your yaml with indentation (yaml is sensitive to indentation).
xample:

# - "ERROR"
# >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
# Enable debug mode for Zowe launch scripts
launchScript:
# Set to "debug" or "trace" to display extra debug information
logLevel: "debug"
# Set to "exit" if you'd like startup to exit if any component has an error
in the configure stage, otherwise zwe will warn but continue.
onComponentConfigureFail: "warn"
# >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
# Default Zowe certificate
#
# **NOTE**: these fields can be updated automatically if you pass
# `--update-config` to `zwe init` command. The generated value will base on
# your setup in `zowe.setup.certificate` section.
certificate:
keystore:
type: JCERACFKS
file: "safkeyring:////ZWESVUSR/ZoweKeyring"
password: password
# # alias is the name of your key/cert. When using keyrings, get the Case
Sensitive, Space Sensitive value in a TSO list ring.
alias: ZOWECNPS
truststore:
# truststore usually has same values as keystore (minus alias), but can be
different if desired.
type: JCERACFKS
file: "safkeyring:////ZWESVUSR/ZoweKeyring"
# file: /global/zowe/keystore/localhost/localhost.truststore.p12
password: password
pem:
key: ""
certificate: ""
file: "safkeyring:////ZWESVUSR/ZoweKeyring&CA ROOT 2048 CNP"

[Jem11111]

Hi, When I put parameters of the default certificat in the similar position as shown by the example-zowe.yaml, I’ve got the problem as you can see in file SYSOUT6. Could you help me to fix this problem ? Thanks, Regards. Jean-Marc De : JoeNemo ***@***.***> Envoyé : mercredi 5 février 2025 17:59 À : zowe/zowe-install-packaging ***@***.***> Cc : MIRANDE-NEY Jean-Marc ***@***.***>; Author ***@***.***> Objet : Re: [zowe/zowe-install-packaging] Need help to have an operational Zowe main server (Issue #4175) There are messages in your log config problems. Maybe an issue near this part of your yaml with indentation (yaml is sensitive to indentation). xample: # - "ERROR" # >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> # Enable debug mode for Zowe launch scripts launchScript: # Set to "debug" or "trace" to display extra debug information logLevel: "debug" # Set to "exit" if you'd like startup to exit if any component has an error in the configure stage, otherwise zwe will warn but continue. onComponentConfigureFail: "warn" # >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> # Default Zowe certificate # # **NOTE**: these fields can be updated automatically if you pass # `--update-config` to `zwe init` command. The generated value will base on # your setup in `zowe.setup.certificate` section. certificate: keystore: type: JCERACFKS file: "safkeyring:////ZWESVUSR/ZoweKeyring" password: password # # alias is the name of your key/cert. When using keyrings, get the Case Sensitive, Space Sensitive value in a TSO list ring. alias: ZOWECNPS truststore: # truststore usually has same values as keystore (minus alias), but can be different if desired. type: JCERACFKS file: "safkeyring:////ZWESVUSR/ZoweKeyring" # file: /global/zowe/keystore/localhost/localhost.truststore.p12 password: password pem: key: "" certificate: "" file: "safkeyring:////ZWESVUSR/ZoweKeyring&CA ROOT 2048 CNP" — Reply to this email directly, view it on GitHub<#4175 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPDYRDCO26RZJ3VGQWHMUPT2OI7OBAVCNFSM6AAAAABWRL2NTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZXGUYDGOJQG4>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et établi à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Internet ne permettant pas d'assurer l’intégrité de ce message, CNP Assurances et ses filiales déclinent toute responsabilité au titre de ce message, s'il a été altéré, déformé ou falsifié. ***************************************************************************** ***************************************************************************** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither CNP Assurances nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.

[Jem11111]

Hi, When I put parameters of the default certificat in the similar position as shown by the example-zowe.yaml, I’ve got the problem as you can see in file SYSOUT6. Could you help me to fix this problem ? Thanks, Regards. Jean-Marc De : JoeNemo ***@***.******@***.***>> Envoyé : mercredi 5 février 2025 17:59 À : zowe/zowe-install-packaging ***@***.******@***.***>> Cc : MIRANDE-NEY Jean-Marc ***@***.******@***.***>>; Author ***@***.******@***.***>> Objet : Re: [zowe/zowe-install-packaging] Need help to have an operational Zowe main server (Issue #4175) There are messages in your log config problems. Maybe an issue near this part of your yaml with indentation (yaml is sensitive to indentation). xample: # - "ERROR" # >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> # Enable debug mode for Zowe launch scripts launchScript: # Set to "debug" or "trace" to display extra debug information logLevel: "debug" # Set to "exit" if you'd like startup to exit if any component has an error in the configure stage, otherwise zwe will warn but continue. onComponentConfigureFail: "warn" # >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> # Default Zowe certificate # # **NOTE**: these fields can be updated automatically if you pass # `--update-config` to `zwe init` command. The generated value will base on # your setup in `zowe.setup.certificate` section. certificate: keystore: type: JCERACFKS file: "safkeyring:////ZWESVUSR/ZoweKeyring" password: password # # alias is the name of your key/cert. When using keyrings, get the Case Sensitive, Space Sensitive value in a TSO list ring. alias: ZOWECNPS truststore: # truststore usually has same values as keystore (minus alias), but can be different if desired. type: JCERACFKS file: "safkeyring:////ZWESVUSR/ZoweKeyring" # file: /global/zowe/keystore/localhost/localhost.truststore.p12 password: password pem: key: "" certificate: "" file: "safkeyring:////ZWESVUSR/ZoweKeyring&CA ROOT 2048 CNP" — Reply to this email directly, view it on GitHub<#4175 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPDYRDCO26RZJ3VGQWHMUPT2OI7OBAVCNFSM6AAAAABWRL2NTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZXGUYDGOJQG4>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et établi à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Internet ne permettant pas d'assurer l’intégrité de ce message, CNP Assurances et ses filiales déclinent toute responsabilité au titre de ce message, s'il a été altéré, déformé ou falsifié. ***************************************************************************** ***************************************************************************** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither CNP Assurances nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.

[Jem11111]

Default cert6.pdf
SysoutJem6.pdf
YAMLjem6.pdf

[MarkAckert]

You can comment out the entire pem block when using keyrings with Zowe. If you do that, the schema should pass.

Separately, the pem block is invalid. file is not a valid field and should instead be certificateAuthorities. Don't worry about this if you're sticking to keyrings.