Integration Update Sets

• Scheduled Data Extract – Ability to export data to mid server or an FTP server on a scheduled basis. Mid server plugin must be installed.
  • MID Server plugin must be installed
  • Documentation: http://www.servicenowguru.com/integration/exporting-report-ftp/
• Microsoft Service Center Operations (SCOM)
  • SCOM plugin must be installed.
  • SCOM connector should be installed on SCOM server.
  • Documentation: http://wiki.service-now.com/index.php?title=Microsoft_System_Center_Operations_Manager_SCOM_Integration
• WiPro Remedy – Bi-directional integration with Remedy via WiPro.
  • System web services plugin must be installed.
  • Documentation: http://wiki.service-now.com/index.php?title=Remedy_Wipro_Integration
• Accenture Remedy – Bidirectional integration with Remedy via Accenture. System web services plugin must be installed.
• Interlink Business Enterprise Server (BES) – Bi-directional integration for alerting
  • System web services plugin must be installed
  • Mid server plugin should be installed.
  • Documentation: http://www.servicenowguru.com/integration/bes-integration-interlink/
• Plugin Creator – Convert an update set into a Service-now Plugin. Mid server plugin and the system update sets plugin must be installed.
• Single Sign-on — Digested Token with Time Condition – Adds a new installation exit that adds the ability to only allow a digested token that was sent within a 5 minute before/after window.
• OpenID – Deep-link support. Adds the ability to preserve a deep link when doing SSO via OpenID. For example, if you attempted to go to a specific incident but were not logged in, the current plugin will log you in via OpenID, but then take you to the main SN page. This update preserves the deep link and takes the user to the intended record.
  • Integration – OpenID SSO plugin must be installed
  • Documentation: http://wiki.service-now.com/index.php?title=External_Authentication_%28Single_Sign-On_-_SSO%29#OpenID
• Single Sign-on — Digested Token with Time Condition – Adds a new installation exit that adds the ability to only allow a digested token that was sent within a 5 minute before/after window.
• Outbound Single Sign-on via Digested Token – Allows Service-now to call send an external web application a digested token in order to login via SSO.  This assumes that the 3rd-party web application has implemented the digested token SSO as described here.
  • Documentation: http://www.servicenowguru.com/integration/outbound-single-signon-digested-token/
• SOAP Attachments – Receive attachments via SOAP.  You’ll send the data to the ecc_queue. Set the following fields:
  • source:  tablename:sysid
  • name:  filename:content-type
  • payload: base64 encoded binary data