DX NetOps

Hello,

we had a customer reporting that the URL for the context-sensitive drill-down from Spectrum 9.3 to IM 2.3 is not rendered properly. Looking at our own installation I was able to reproduce the problem. The Java renderer used doesn't seem to populate all necessary fields to create a valid URL (see attached screenshot).

However I also found a workaround which I want to share with you.

The file where the menu item is configured in Spectrum can be found here:

/opt/spectrum/tomcat/webapps/spectrum/WEB-INF/netqos/config/netqos-app-config.xml

The following code in the netqos-app-config.xml file is responsible for creating the link to the Performance Center menu we find the Right-Click menu:

<launch-browser>
          <url>{0}</url>
          <param>
             <renderer>com.ca.im.netqos.integration.client.render.NetqosURLLaunchRenderer</renderer>
          </param>
</launch-browser>

As we can see CA uses a Java render creating the URL and putting all the information in. As we cannot really fix the Java code, I came up with the following work-around:

<launch-browser>
           <url>http://192.168.53.50:8181/pc/desktop/page?pg=sw&amp;DeviceID={0}</url>
           <param>
                 <attribute>0x13214</attribute>
                 <renderer>com.aprisma.spectrum.app.util.render.SimpleIntegerRenderer</renderer>
           </param>
</launch-browser>

We basically have to hard-code the URL and port information into the code. The only thing that differes for each context-sensitive drill-down link is the ItemID for the device in CA IM 2.0. Luckily this is also being saved in the attribute 0x13214. So I use this and dynamically pass it to the URL. This allows us to be still context sensitive, yet have a working drill down into CA IM 2.0. To get it to work on your system you have to change the IP address shown in the example with the IP address of your Performance Center.

I also posted this in the Spectrum community as a response to Carlos, who already encountered a similar problem a few days ago. An official support ticket is also open.

Hope that helps.

Greetings,

Ben

Nice work on that, thanks for sharing.

Actually it has a glitch and is not as dynamic as I thought. The reason is that CA also passed the device type in the URL, as there are different pages to represent the different device types. This could be mapped using the Model_Class attribute and do a mapping. Again this is supposed to be a workaround for everyone who wants to play around with this.

<launch-browser>
                <url>http://192.168.53.50:8181/pc/desktop/page?pg={0}&amp;DeviceID={1}</url>
                <param>
                        <select>
                                <case>
                                        <expression><!-- Model Class ID for Switch-->
                                         attrInt(0x11ee8) == 2
                                        </expression>
                                        <yield>
                                        sw
                                        </yield>
                                </case>
                                <case>
                                        <expression><!-- Model Class ID for Router-->
                                         attrInt(0x11ee8) == 3
                                        </expression>
                                        <yield>
                                        r
                                        </yield>
                                </case>
                                <case>
                                        <expression><!-- Model Class ID for Workstation-Server-->
                                         attrInt(0x11ee8) == 9
                                        </expression>
                                        <yield>
                                        s
                                        </yield>
                                </case>

                        </select>
                </param>
                <param>
                        <attribute>0x13214</attribute>
                        <renderer>com.aprisma.spectrum.app.util.render.SimpleIntegerRenderer</renderer>
                </param>
        </launch-browser>

Of course this is not complete, but now at least it more dynamic than before. As Spectrum has a lot more Modell_Classes would need a mapping this needs a bit more work, if you want to cover your whole environment. It's a workaround but not a solution, as CA needs to fix the interface.

Hey Benny,

you may also check the following on your OCE:

---

The root URL of CAPC is from the CAPC_URL_Prefix attribute on NetqosIntegrationManager model and usually it looks like:

http://1.2.3.4:8181/pc/desktop/page.

If the URL is not correct, then you can check the above attribute value to see if it is set correctly.

---

So you might not need to adjust the xml files ...

But sso is still not working when jumping to CAPC.

 

rgds Steve

 

Hi Steve,

thanks for the hint :-)

Happy New Year btw

Hey Benny,

well, same for you! ;)

rgds Steve

Hello,

seems to be fixed in IM 2.3.2. No workaround longer needed here (Spectrum 9.3 H01 / IM 2.3.2).

rgds Sebastian