Service Mapping - Apache on Windows WAS connectivity

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2017 10:19 AM
I am attempting to map IBM's Maximo application (app and web are WebSphere and Apache running on Windows, database is Oracle running on Solaris) via Service Mapping. Identification looks good in Apache, and I see green for every step in WAS Connectivity, but the WAS Connectivity section itself is red, and the WAS instances are not being discovered.
Traffic-based discovery brings WAS into the map, and the WAS instances are on the same servers as their corresponding web servers, so I am kind of at a loss. I'm also pretty new to mapping (I've taken the class), and this is the first time we've tried to do anything with mapping.
I'm attaching the logs for the Apache on Windows pattern.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2017 06:00 AM
Hi John!
I highly recommend debugging this step by step. In viewing the log file you provided, focus on the steps that filter hosts or perform any merging of table data. My initial thought, is something isn't matching, and you may need to make a pattern modifiation to support WAS within your organization.
If you do make modifications, I highly recommend any steps that are modified or added, you prefix with --- Mod or ---Add so it is easy to see the differences during patches and upgrades to the base platform.
Thanks
Sarah

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2017 08:03 PM
Hi John, most likely this is a pattern related issue. Please follow the troubleshooting steps described in the documentation below so you can pinpoint where exactly is the issue:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2018 08:40 AM
I have the same issue. What I found was that in the Apache on Windows pattern, identification section. In steps 10 and 11, default location of config file, there are forward slashes where they should be back slashes. Once I fixed that we got to where it would work through the WAS connectivity section but doesn't actually download the WAS plugin XML file. The issue is with the variable $wasplugin, if you debug and feed it a string with the file path (with double backslashes, ie c:\\folder\\plugin-cfg.xml) then it will grab the file successfully and parse it. As the variable stands, in step 3 where it is supposed to download the file it fails. My thought it manipulate the variable between steps 2 and 3 but that is where i'm getting stuck. I need to replace all the forward slashes with double backslashes but I'm failing to see how to do so with the Parse Variable operation...