Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

SWIS detection issue on NPM 9.5...

Our NPM app is out in beta and one of our users is having issues with our app detecting his NPM instalaltion.

User is running NPM 9.5, SWIS service confirmed running.

We make a simple GET to OrionServerAddress:17778/.../InformationService just to confirm the service exists before authentication.

When our user types OrionServerAddress:17778/.../InformationService into a browser they do not get a return.

Is there a way to change the ports that SWIS listens to or have there been changes to service endpoints/protocols between 9.5 and 10.x?

Find more posts tagged with

Accepted answers

tdanner

NPM 9.5 does not have HTTPS access to SWIS out of the box, but it can be added through some configuration changes. The 1.0 release of the Orion SDK included step-by-step instructions for doing this and also a tool that can automate the process. Your user will need to either follow the instructions or run the tool to set up HTTPS access to SWIS.

Once that's done, the SOAP contract for queries and method invocation will be the same as in the current release. However, NPM 9.5 does not support CRUD (e.g., adding nodes). It also may not support all of the schema elements you are using in 10.x.

I'll send you the 1.0 version of Orion SDK by email. If you want to install it on a machine that already has a later version of the SDK, you will need to uninstall the later version first - it won't downgrade you.

All comments

tdanner

mattmoore

FYI, the Orion 9.5 user was able to retrieve basic and advanced alerts but received 'RunQuery failed' exceptions when accessing nodes and interfaces.

tdanner

There have been some properties added to nodes and interfaces since 9.5. Maybe your query was using one of them? The exceptions should mention the name of the property if that is the issue.

mattmoore

I figured that.

Unfortunately all I get is 'RunQuery failed' error.

I've tried to dive deeper down into the exception to get the property that failed but I can't seem to find it.