whitepaper: Amdocs Web Service Factory

advertisement
Amdocs Web Service
Factory
Amdocs Web Service Factory | 2
Contents
Executive Summary..................................................................................1
Architecture..............................................................................................3
Components............................................................................................5
Service Design.........................................................................................7
Service Implementation............................................................................9
Amdocs Web Service Factory | 3
Executive Summary
The Amdocs Web Service Factory (WSF) provides highquality web services exposing the Amdocs portfolio API’s
to external systems. WSF web services provide a coherent,
precise and well-documented interface based on a common
information model - the Amdocs Portfolio Information Model
(PIM), which is an implementation of the TMF SID model.
WSF focuses on interoperability and integration, providing a
thin abstraction layer – on top of the Amdocs product API’s
– that mediates between the web service interface and
the product-specific interface. WSF enables evolutionary
refinement by decoupling the public interfaces from the API
implementation and allowing for effective service versioning.
The WSF runtime infrastructure is based on leading,
industry-standard, open-source components, such as
Apache Tomcat, that have a proven, reliable track record
and provide a scalable architecture.
WSF employs a “factory-style” release process by which
bundles of services are released on a recurring basis – with
no dependence on the general Amdocs product release
cycle. This independence enables the “factory” to respond
to changing customer priorities and market developments.
WSF reduces project costs by saving the customer from
having to map Java-based product API’s to XML-based
web services. Customization time is further reduced by the
adoption of common data structures and best practices.
WSF is designed for consumption by ESB’s and BPM
tools without additional customization, and it handles all
integration aspects (such as security) reducing the need for
custom solutions.
Amdocs Web Service Factory | 4
Architecture
WSF services mediate between the common information
model provided by the web service interface and the
product-specific model provided by each product’s API.
web service interfaces with
consistent data semantics based on
a common information model (sid)
External
esb/bpm
http(/s)/soap
Interoperability is
the highest
priority here!
web
service
gateway
tomcat / cxf
PRODUCT API’s WITH PRODUCT SPECIFIC
INFORMATION MODELS
cm
replenishment
ar
srm
ejb/rmi(/ssl)
Performance is
the highest
priority here!
Figure 2.1 Web Service Factory Architecture
WSF web services are deployed to a gateway implemented
using the Spring framework and Apache CXF, and hosted by
Apache Tomcat. The gateway handles all aspects of security
using the WS Security standard, supporting stateless
username/password credentials, and SAML token.
ordering
invoicing
sales
engine
online
charging
MCSS
CRM
Amdocs Web Service Factory | 5
Components
WSF consists of three principal components:
A Software Development Kit (SDK) comprising:
• Development guidelines
• Data type vocabulary
• Validation tools
• Reference source code of provided web services
• Packaging and configuration tools
• Eclipse STS (Spring Tool Suite) for development
• Apache Maven for build
• A Runtime environment comprising:
• Monitoring capabilities (Amdocs Monitoring Framework)
• Tomcat server for service deployment
• A Web service bundle containing well-designed services
according to delivery priorities and broken down to
atomic operations required by customers.
Amdocs Web Service Factory | 6
Service Design
WSF web service design is inspired by the UN/CEFACT CCTS
standard. All services operate on a common information
model that defines the vocabulary and semantics of the
information. Each service operation uses a subset of this
model appropriate to the business context of the operation.
These business context models are a restriction of the
common model according to well-defined rules.
Common Model
The common model includes all types in the information
model, and is unqualified by any business context.
These types are copied and restricted to form qualified
business context models used by the services.
XSD
Service
Validation here ensures that
the service model is a proper
qualification of the common model
Figure 4.1 Service Design for Web Service Factory
Validation
Validation
Business
Context Model
Web services are designed by means of a model-first
approach. The model is expressed in annotated Java that
acts as metadata for the resulting WSDL and XSD. Java
is used to leverage the sophisticated tooling provided by
Eclipse.
WSDL
Validation here ensures
that the WSDL complies to
WS-I B(S)P 1.x.
Amdocs Web Service Factory | 7
Service Implementation
The WSDL/XSD is imported into Apache CXF, to generate
the Service Endpoint Interface (SEI) and the implementation
skeleton.
Mapping of the contract to the backend API is done
manually as a part of this phase.
The finished service is built into a WAR for deployment.
XSD
JAVA
WSDL
Figure 5.1 Service Implementation for Web Service Factory
war
About Amdocs
For 30 years, Amdocs has ensured service providers’ success and embraced their biggest challenges. To win in the connected world, service
providers rely on Amdocs to simplify the customer experience, harness the data explosion, stay ahead with new services and improve
operational efficiency. The global company uniquely combines a market-leading BSS, OSS and network control product portfolio with
value-driven professional services and managed services operations. With revenue of $3.2 billion in fiscal 2012, Amdocs and its 20,000
employees serve customers in more than 60 countries. Amdocs: Embrace Challenge, Experience Success. For more information, visit
Amdocs at www.amdocs.com
Amdocs has offices, development and support centers worldwide, including sites in:
THE AMERICAS:
ASIA PACIFIC:
EUROPE, MIDDLE EAST & AFRICA:
BRAZIL
AUSTRALIA
Austria
ISRAEL
SPAIN
CANADA
CHINA
CYPRUS
kazakhstan
SWEDEN
COSTA RICA
INDIA
CZECH REPUBLIC
THE NETHERLANDS
UNITED KINGDOM
MEXICO
JAPAN
FRANCE
POLAND
United Arab Emirates - Dubai
UNITED STATES
Philippines
GERMANY
RUSSIA
Singapore
IRELAND
SOUTH AFRICA
Taiwan
THAILAND
VIETNAM
For the most up-to-date contact information for all Amdocs offices worldwide, please visit our website at www.amdocs.com/corporate.asp
Copyright © 2013 Amdocs. All Rights Reserved. Reproduction or distribution other than for intended purposes is prohibited, without the prior written consent of Amdocs. The trademarks and service marks of Amdocs, including the Amdocs mark and logo,
Intentional Customer Experience, CES, Clarify, Ensemble, Enabler, Return on Relationship, Intelecable, Collabrent, XACCT, DST Innovis, Stibo Graphic Software, Qpass, Cramer, SigValue, JacobsRimell, ChangingWorlds, jNetX, OpenMarket Inc., MX Telecom Inc., MX
Telecom Ltd, Streamezzo, and Bridgewater Systems are the exclusive property of Amdocs, and may not be used without permission. All other marks are the property of their respective owners. Created 01/2013
Download