Sunday, Sep 05, 2010
Login

Posts Tagged ‘Integration’

Outbound Single Sign-on via Digested Token

S

ervice-now makes configuring SSO into your Service-now instance very simple.  By enabling a plugin and configuring a couple of properties, single sign-on can be set up in less than 10 minutes.  Documentation surrounding these SSO methods are also well done and easy to follow.

Recently, I’ve come across a number or clients that want to use Service-now as their main company portal and wish to configure their Service-now instance to generate an SSO token that can be consumed by a third party service provider.  In other words, they desire to have outbound single sign-on directed to of their other internal applications.  Because of this increasingly common request, I have created an update set that can be used for such a purpose called, Outbound Single Sign-on via Digested Token.


Sending attachments to a 3rd-party service desk

L

ast week I wrote about how to send a file to Service-now via web services and attach it to a target record.  While that is the most common request for attachment handling in regards to an integration, I often hear requests for this to be bidirectional.  Sending attachments from Service-now to a third-party system isn’t something that we’ve actually implemented in the past.  However, with the number of people asking for it lately, I decided to write up a solution.


Sending an attachment to Service-now via Web Services

A
ttaching a file to a record within the Service-now interface is a trivial task.  However, many customer have found it necessary to send an attachment via web services to Service-now.  This need is usually spawned from an integration with a 3rd-party product.  The SOAP Attachments update set is the perfect solution for this problem. The update set has now been added to the latest release of Service-now as part of the core code.  You will only need this update set if you’re on an older build.


Exporting a Report Directly to FTP

Scheduled Data Extract

S

ervice-now provides numerous ways of getting data into the system. The import set functionality supports pulling data in from an attachment, FTP(S) servers, JDBC data sources, etc. However, a common problem that many customers have is trying to get data out of their SN instance and into their data center. The simplest way to handle this currently is by having a report emailed to you on a scheduled basis. There has to be a better way!

Scheduled Data Extract ModulesThe good news is that there is a better way. The “Scheduled Data Extract” update set has been designed to allow a user to have reports, tables, or table views sent to a specific directory on a local mid server or FTP to a customer’s FTP/FTPS server on a scheduled basis. The “Scheduled Data Extract” update set has been battle-tested and is used by several large Service-now customers today.


Extending the CMDB

O

ne of the most basic needs that a customer has when building out their CMDB is extending it to match the types of CIs that they’re currently using in their company.  This is especially true when bringing data in from a 3rd-party CMDB (such as IBM’s CCMDB, HP’s uCMDB, etc) with Service-now.  Some of these CMDBs have hundreds of class types with scores of fields for each class.  How can you get the 3rd-party data into Service-now when the schema is so different?

There are essentially four main steps to accomplish this: decide what classes and fields need to be brought across, create a mapping document, extend the Service-now CMDB to accept the new classes, and send the data from the 3rd party CMDB to Service-now.


 

Recent Comments

  • Scott Stechmesser: Awesome script to use. Works great. How would you modify it to be able to copy a Catalog UI Policy?
  • Tulio: Perfect!!! Thanks for this.
  • Ron Methias: Another reason why I have stopped going to the official SN documentation sites and make the GURU my...
  • Richard Huss: Ingenious – and somewhat simpler than the way the Incident Resolution best practice plugin does...
  • valor: Joe, that’s one of the reasons why I’m parsing out the URL instead of trying to get the page...