This post is part of a series exploring the unique aspects and capabilities of WebSphere Liberty when running on z/OS.
We'll also explore considerations when moving from WebSphere traditional on z/OS to Liberty on z/OS.
The next post in the series is here.
To start at the beginning, follow this link to the first post.
---------------
In earlier posts we’ve looked at what the Angel is and how it works with the server (if you’re joining late, follow the link above to the first post in the series where you’ll find an index of all the posts…go find the Angel related ones and have a read, we’ll wait…..)
Ok, so today we’re going to look at the messages issued by the server as it establishes (or doesn’t) its connection to the Angel.
Best case you’re looking for message CWWKB0122I which tells you the server has connected to an Angel. Included in the message is the name of the Angel (or ‘default’ if connecting to the default Angel).
If it doesn’t work, you’ll get CWWKB0010I which includes a reason code. Most likely the Angel you’re after isn’t up or you don’t have SAF access to the required stuff. The reason code itself is internal so give us a holler if it doesn’t seem to be anything obvious.
It is also possible to make connecting to the Angel required. By default if we can’t connect we’ll just muddle on with out it, but in some situations you might know you have to have an Angel and can tell the server not to finish initializing without it. If you do that, it is also possible to configure a wait-time to wait for the Angel to turn up. If you start both server and Angel at the same time it is possible the server might look for the Angel before it gets all its bits in place. Configuring the wait-time will allow some leeway for the Angel to be ready before the server gives up.
If you’ve done that stuff, you’ll see CWWKB0124I which tells you the Angel is required and what the configured wait-time is (which might be zero if you didn’t set it).
The last message we’ll look at in this post is CWWKB0129I which gets issued if you’ve configured required Angel services (about which there is an earlier blog post). If you’ve specified required services then they will be listed here in this message.
All that should let you know where you server is regarding just connecting to an Angel. Once it has done that, it will try to work out which services are available via the Angel and which ones your server is allowed to use. That will be covered in our next post….