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.

To start at the beginning, follow this link to the first post.

---------------

If you’ve got a web application installed in your server then there are a whole bunch of messages you can get if things aren’t set up properly.  But if everything is (relatively) fine then you should get CWWKT0016I.  Here’s an example that I lifted from somebody else’s blog post:

CWWKT0016I: Web application available (vhost): http://localhost:9082/SimpleServlet/

The thing in parenthesis is the virtual host so you will often see ‘default_host’ shown here if you haven’t done anything to make it use something else.

The rest of that message is a URL you can use to access the application.  Note that I said ‘a’ URL and not ‘the’ URL.  There can be more than one, but you’ll only get one message that lists one of them.  So it is good to look for this message and make sure what shows up here is something you’re expecting. 

This message is also very handy if you’re doing a demo of some sort and you need to quickly grab something you can use to drive your demo.  Cut/pasting this URL will (usually) get you what you need.

As we’ve discussed about other messages, there are a lot of other messages in the neighborhood that can indicate problems.  And, as before, I’m not going to try to list them here.  You may want to search online for that message ID to find where its (minimal) documentation lives and then kind of browse around to see what other kinds of messages can come out in this neighborhood.  I’ve found that having some familiarity with error messages you’re not getting can be useful when you have a problem.  If you know that there’s a message for error-X and you know you didn’t see that message, you can quickly eliminate a cause of your problem.  For example, if you know about message CWWKT0015W (no ports configured for endpoint) and you know you didn’t get that message, then you know that’s not the problem.  I’m not suggesting you should memorize all the possible messages (I kind of remember reading in Richard Feynman’s memoirs that Neils Bohr had memorized the logarithm tables…so if you’re that kind of person, go for it).  But just having a vague familiarity with the things that can go wrong can sometimes help. 

Or not.

One last thing…there’s also a CWWKT0017I message that gets issued when the application is removed…if you’re dynamically updating your server configuration.