7 - sm7 ie class slides, module 7 (integration) as of 10-28

8/2/2019 7 - SM7 IE Class Slides, Module 7 (Integration) as of 10-28

1/45

M7.00 I.E.


2/45

M7.00 I.E.


3/45

sentation Title

Instructor notes[Copy and paste this textbox on notes pages for allslides]


4/45

sentation Title


5/45

sentation Title

SOAP Server-

API Server- special case of the SOAP Server- no port redirect

single threaded- 1 port per user (dedicated instance per app)

consults the Doc Eng to learn what to expose in WSDL

Document Engine- abstraction of RAD

Apps- essentially RAD with Tailoring

WSDL- compile time binding


6/45

sentation Title



7/45

sentation Title

Before diving into concepts and terminology, I thought it would be a good idea to try toconvey something about the purpose and the value of web services. This graphic is myperspective on that.

Web services is the latest technology for application integration. It is superior to earliertechnologies because:

It is standardized by organizations like W3C, WS-I, etc.

It is based on widely available non-proprietary web technology, such as HTTP, XML, etc.

Vendor agnostic, not controlled by any single company

As long as everybody plays by the rules, you can mix and match WS tools andimplementations

Tools and Web Service implementations interoperate with no vendor communication orcooperation required, for example:

Applications developed using Microsoft Visual Studio .NET work with Service Manager 7

Applications developed using Axis work with Service Manager 7

Applications developed using Service Manager 7 work with all 3 rd party web services wehave so far encountered


8/45

sentation Title

WSDL is a W3C (World-wide Web Consortium) standard for describing web services. AWSDL file is an XML document. A WSDL file describes the API calls (if you will) of theweb service. In WS terms, these are called SOAP operations, or methods as they are oftencalled. The WSDL also describes the inputs and outputs of a web service in terms of XMLmessages. And it gives information about the location of the web service, typically an HTTPURL.

Typically, the programmer doesnt read WSDL directly, one uses some sort of SOAP -enabled application development toolkit to process WSDL into code, as in the screen shotwe looked at a moment ago. The toolkit you choose is up to you. So instead of needing avendor SDK, you just pick some toolkit of your choice for the platform you want your SOAPclient application to run on.

Ive listed some popular web services tools that developers use to create applications with.The last one, wsdl2js, is a HP-provided utility first developed in ServiceCenter 6.1.Developing a SOAP client application to consume a web service is basically a two-stepprocess. First you generate code from the WSDL, then you fill in the blanks so -to-speak tomake the generated code do something useful. This can be a pretty simple process aswell see in a moment. Service Manager 7 will ship with Java samples for Axis, C# samplesfor .NET, and some Javascript samples within the Service Manager 7 script library.


9/45

sentation Title

With web services, we tend not to use the terms client andserver, but they are applicable. If we say application XYZexposes a web service (or web services) which we mean thatapplication XYZ can act as a SOAP server which will respond torequests from a SOAP client. We also like to speak of anapplication as consuming a web service, and this just meansthat the application is a client of that web service.

SC 6.0 can serve web services, without the customer having towrite any code, and SC 6.1 improves substantially on thisprocess, but the Service Manager application developer in 6.0has no way to invoke a web service in some other enterpriseapplication, such as Peoplesoft, or SAP or whatever, or ahomegrown web service, which a lot of customers are starting tobuild, or at least plan for. Now in SM 7, this can be done, usingJavascript, and a new tool called WSDL2JS, which well see ademo of in a moment. The acronym RPC stands for RemoteProcedure Call. By RPC programming model we mean thatfrom the viewpoint of the programmer, invoking a web service isa lot like RPC. Well see a live example of this in a moment.



10/45

sentation Title



11/45

sentation Title

So, SM 7 has the ability to consume web services from Service Manager 7 JavaScript applications,but there are also major improvements to the way Service Manager publishes web services in 7.

First and foremost, Service Manager 7 exposes its web services in a way that is SERVICE orientedas opposed to file-oriented. The older approach is now deprecated. The new API uses ITIL

terminology, not legacy ServiceCenter terminology. In SC 6.0, you had to know that to create anincident, you had to manipulate the probsummary file. Specifically, you had to do a probsummaryAddoperation on it. In SM7, this requirement to know historic ServiceCenter terminology goes away. SM7exposes an IncidentManagement service, which describes an object called an Incident, and defines aset of operations like CreateIncident, UpdateIncident, ResolveIncident, and CloseIncident. And thefields contained in an Incident object have rational names, rather than ambiguous or historic names.We use IncidentID rather than number for example. Well look at how this renaming or aliasingworks later. And we also are excluding most of the fields in probsummary from the new Incidentobject. Only about 10% or less of the fields in probsummary are needed for most applications.Frankly, theres a lot of historic stuff that has accumulated in probsummary over the years due to theinability to delete fields from files in ServiceCenter due to legacy requirements. In SM7, we no longerpublish these old fields, via an exclusion facility well look at later. Another important aspect of theWSDL in SM7 is that it groups all the files you need together into a service. In 6.0, if you wanted tocreate a SOAP application to do change management related things, you had to not only know aboutcm3r and cm3t, but you had to make separate WSDL requests for those files and combine the

resulting generated code into one project. In SM7, this is done automatically. All of this grouping,aliasing, and exclusion functionality can be thought of as an abstraction layer that protects customer SOAP applications from changes in the low-level Service Manager schema. If we decide to do awaywith the file known as probsummary in some future applications release, a SOAP client whichmanipulates Incidents will still work.


12/45

sentation Title

So, SC 6.1 has the ability to consume web services from Service Manager 7.1 Javascriptapplications, but there are also major improvements to the way Service Manager publishes webservices in 6.1

First and foremost, Service Manager 7.1 exposes its web services in a way that is SERVICE oriented

as opposed to file-oriented which is the way it was done in 6.0. The older approach is nowdeprecated. A 6.0 application will still work, but we recommend that the new WSDL be used for allapplications going forward. The new API uses ITIL terminology, not legacy Service Managerterminology. In SC 6.0, you had to know that to create an incident, you had to manipulate theprobsummary file. Specifically, you had to do a probsummaryAdd operation on it. In 6.1, thisrequirement to know historic Service Manager terminology goes away. SC 6.1 exposes anIncidentManagement service, which describes an object called an Incident, and defines a set ofoperations like CreateIncident, UpdateIncident, ResolveIncident, and CloseIncident. And the fieldscontained in an Incident object have rational names, rather than ambiguous or historic names. Weuse IncidentID rather than number for example. Well look at how this renaming or aliasing workslater. And we also are excluding most of the fields in probsummary from the new Incident object.Only about 10% or less of the fields in probsummary are needed for most applications. Frankly,theres a lot of historic stuff that has accumulated in probsummary over the years due to the inabilityto delete fields from files in Service Manager. In 6.1, we no longer publish these old fields, via anexclusion facility well look at later. Another important aspect of the new WSDL in 6.1 is that it groups

all the files you need together into a service. In 6.0, if you wanted to create a SOAP application to dochange management related things, you had to not only know about cm3r and cm3t, but you hadto make separate WSDL requests for those files and combine the resulting generated code into oneproject. In 6.1, this is done automatically. All of this grouping, aliasing, and exclusion functionalitycan be thought of as an abstraction layer that protects customer SOAP applications from changesin the low-level Service Manager schema. If we decide to do away with the file known asprobsummary in some future applications release, a SOAP client which manipulates Incidents willstill work.


13/45

sentation Title

So, SM 7 has the ability to consume web services from Service Manager 7 JavaScript applications,but there are also major improvements to the way Service Manager publishes web services.

First and foremost, Service Manager 7 exposes its web services in a way that is SERVICE orientedas opposed to file-oriented which is the way it was done in 6.0. The older approach is now

deprecated. A 6.0 application will still work, but we recommend that the new WSDL be used for allapplications going forward. The new API uses ITIL terminology, not legacy Service Managerterminology. In SC 6.0, you had to know that to create an incident, you had to manipulate theprobsummary file. Specifically, you had to do a probsummaryAdd operation on it. In 6.1, thisrequirement to know historic Service Manager terminology goes away. SC 6.1 exposes anIncidentManagement service, which describes an object called an Incident, and defines a set ofoperations like CreateIncident, UpdateIncident, ResolveIncident, and CloseIncident. And the fieldscontained in an Incident object have rational names, rather than ambiguous or historic names. Weuse IncidentID rather than number for example. Well look at how this renaming or aliasing workslater. And we also are excluding most of the fields in probsummary from the new Incident object.Only about 10% or less of the fields in probsummary are needed for most applications. Frankly,theres a lot of historic stuff that has accumulated in probsummary over the years due to the inabilityto delete fields from files in Service Manager. In 6.1, we no longer publish these old fields, via anexclusion facility well look at later. Another important aspect of the new WSDL in 6.1 is that it groupsall the files you need together into a service. In 6.0, if you wanted to create a SOAP application to dochange management related things, you had to not only know about cm3r and cm3t, but you hadto make separate WSDL requests for those files and combine the resulting generated code into oneproject. In 6.1, this is done automatically. All of this grouping, aliasing, and exclusion functionalitycan be thought of as an abstraction layer that protects customer SOAP applications from changesin the low-level Service Manager schema. If we decide to do away with the file known asprobsummary in some future applications release, a SOAP client which manipulates Incidents willstill work.


14/45

sentation Title






15/45

sentation Title


16/45

sentation Title






17/45

sentation Title



18/45

sentation Title



19/45

sentation Title


20/45

sentation Title



21/45

sentation Title


22/45

sentation Title


23/45

sentation Title


24/45

sentation Title

Streamline business processes by sharing data and processes with multipleapplications

Enable management to make informed business decisions based oncomprehensive infrastructure view

Improve data quality by eliminating redundant data gathering efforts

Pricing is consistent with the value we provide. Connect-It adds a lot of value to thePRGN solutions.

Implementation time is reduced compared to full EAI tools which also costsignificantly more in both implementation time and license acquisition.

Because our tool is so simple, it runs with almost no maintenance.

This is really THE differentiator: our competitors offer single gateways to inventorygathering tools at low price or complex EAI solutions at very high price. We offerbest of both.


25/45

sentation Title


26/45

sentation Title


27/45

sentation Title


28/45

sentation Title

10/19/07 - The SM7 connector won't be available until ConnectIt 3.81, which is due out in a month or so.


29/45

sentation Title


30/45

sentation Title


31/45

sentation Title


32/45

sentation Title


33/45


34/45

sentation Title


35/45


36/45

sentation Title


37/45

sentation Title


38/45

sentation Title


39/45

sentation Title



40/45

sentation Title


41/45

sentation Title


42/45

sentation Title


43/45

sentation Title


44/45

sentation Title


45/45

7 - sm7 ie class slides, module 7 (integration) as of 10-28

Documents