Zowe doesn't establish connection with zosmf

[dsegoviaMF]

We are trying to install and customize ZOWE V2R12 and we always get the following error message after reboot:
2024-02-02 13:01:57.304 ZWEAGW1:Thread-14:67175037 IZUSVR ERROR (o.z.a.g.s.s.JwtSecurity) ZWEAG108E z/OSMF instance 'zosmf' not found or incorrectly configured. Gateway is shutting down.

The only z/OSMS configuration that we have is in the configuration yaml:
Ñ-------------------------------------------------------------------------------
Ñ z/OSMF configuration
Ñ
Ñ If your Zowe instance is configured to use z/OSMF for authentication or other
Ñ features. You need to define how to access your z/OSMF instance.
Ñ-------------------------------------------------------------------------------
zOSMF:
Ñ COMMONLY_CUSTOMIZED
Ñ host name of your z/OSMF instance
host: zowes.xxxx.xx
Ñ COMMONLY_CUSTOMIZED
port: yyyy
applId: IZUDFLT

We know that the hostname and port are correct, z/OSMF responds correctly to https://zowes.xxxx.xx:yyyy/info

What we are not clear about is the value to put in the applId parameter, it is the default value of the yaml. Do you know what we should indicate in that parameter?

On the other hand, reviewing the log messages prior to ZWEAG108E we do not see any related to the attempt to register z/OSMF in discovery.

Do you know who should start the registration and what type of connection uses? Is it a secure connection? How is authentication done?

In case it was a problem related to the certificate, which we have in a RACF keyring, we have configured verifyCertificates: DISABLED, but we get the same result

Agradeceríamos nos echaras una mano, no sabemos por donde tirar.

We would appreciate if you could help us with our problems.

[zFernand0]

Hey @dsegoviaMF,
Thank you for opening the discussion.
I believe this might be better suited for the Zowe APIML repository.
Transfering!

[achmelo]

Hi @dsegoviaMF , if you have default zOSMF installation then IZUDFLT is the correct APPLID, otherwise, you would need to consult your installation for more details. However, APPLID is not related to your issue because it is not used in this place. zOSMF is registered statically, which means there is a yaml definition in the Zowe workspace directory, location: runtime/instance/workspace/api-mediation/api-defs. This file is in UTF-8 encoding. Please look here first to see whether the zOSMF configuration is correct. The next step in the debugging would be to enable Gateway to debug logs. This will provide more data about HTTP requests to zOSMF in case it is properly registered in Discovery service.

[balhar-jakub]

@dsegoviaMF Is there any update from your side or should we close the discussion?