The current version of 'CRM Webservices Framework includes:
- 7.2 Compatible
- Built in X3 Connector
- Built in X3 interfaces
- Built in X3 Account Migration and Synchronisation
- Increased error handling on Installer
- New Connector class library structure in Gateway source
- Enhanced interface behaviours on Block objects
- Enhanced Record object behaviours including nested ADO record references for X3
- Editable Grids for List objects in Edit Mode
- Field Level Script support for Screens and Lists
- Table Level Script support for Webservice based entities
The following components make up the complete infrastructure of a Webservice Framework deployment. Depending on the implementation, some components may not be required or there may be a requirement to extend the functionality required, notably within the Enbu Gateway. This allows for an extended set of options within this generic module to deliver an Enterprise Service Bus solution.
The Framework Control Panel is the entry point to interactively access all components that make up the Enbu Webservice Framework.
You can access the Enbu Gateway directly from here and check that the service is up and running. Each of the methods of the servcies can be invoked and the return values analysed etc.
The Gateway Monitor is a utility that allows a view of all running details of the Enbu Gateway. This includes a display of all current configuration details that is being used be the Gateway configuration file.
The Monitor page automatically refreshes itself so you may analyse real time processing of Transactions as they occur within the Gateway.
Other than the Enbu Gateway, the Framework Broker is the other fundamental module of the Webservice Framework. They Enbu Gateway works hand in hand with the Framework Broker whereby the Broker does all the work that the Gateway needs in terms of CRM functionality and data. In an expanded deployment of the Webservice Framework with multiple connected services other than Sage CRM, each of these systems would need their own variation of a ‘Broker’ to send and receive messages to and from the Enbu Gateway.
The Broker Test Form is a utility within the Framework Control Panel of CRM. This utility allows for direct access to the Framework Broker without relying on the Enbu Gateway to call it. This allows for work to be developed within the Broker independent of the Gateway but also helps to understand the returned values from the Broker and diagnosis any issues that may occurring.
Testing the Execute methods allows for interative loops of requests to be run upon the Gateway mainly testing the CRM based requests. A sample FindRecord request is supplied but any Gateway XML message content can be added here. Note that this type of request is going to the Enbu Gateway first and therein passing on the request to the Broker and returning the values received back to the Test Harness. This is different to the Test Broker Form as the Broker Form bypasses the Enbu Gateway. In this Test Harness, it is a full connectivity test from Client (CRM Test Harness in this case), Gateway, Broker and back again.
Companies Listing Using the Demo Webservice in this test, we show how Webservices based data can be shown within CRM using familiar interfaces of Lists, Screens and Fields. It shows how to manage full create, read, update and deletion operations on Webservices data whereas the User just sees the normal operation of data over these CRM interfaces.
Text Merge using Demo Webservice as another example of how the Framework API can be used, we set up a call to the Demo Webservice to retrieve data and then use the TextMerge() function supplied to work in Webservice data as a record into an email/text template. This illustrates different ways to consider how the Webservices Framework can be used within CRM to populate and represent data from multiple systems, all connected to the Enbu Gateway.
The Windows Communication Foundation (or WCF), previously known as “Indigo”, is a runtime and a set of APIs (application programming interface) in the .NET Framework for building connected, service-oriented applications.
A Web Service is programmable application logic accessible via standard Web protocols. One of these Web protocols is the Simple Object Access Protocol (SOAP). SOAP uses standards based technologies (XML for data description and HTTP for transport) to encode and transmit application data. Consumers of a Web Service do not need to know anything about the platform, object model, or programming language used to implement the service; they only need to understand how to send and receive SOAP messages (HTTP and XML).
Windows Communication Foundation (WCF) is a framework for building service-oriented applications. Using WCF, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application. An endpoint can be a client of a service that requests data from a service endpoint. The messages can be as simple as a single character or word sent as XML, or as complex as a stream of binary data.
The current version of CRM Webservices Framework includes:
- Enhanced Gateway
- Improved Framework Control Panel
- CRM Broker Module which allows complex data to be processed
- WCF Gateway Implementation of the Webservices
- Gateway Monitor Module for multi threaded analysis
- CRM Test Harness to run test analysis, functions and third party integration
- Allow CRM absorb and utilise 3rd party Webservice connections
- Create a new highly scalable CRM Webservice which can be utilised by other systems.
- Allow CRM to be integrated into high scale SOA architectures and even deliver an Enterprise Service Bus which can be utilised by surrounding systems.
- Provide a set of utilities to manage and monitor the activities around this Framework
- Bidirectional Webservice Data and Connectivity
- Customisation of Objects and Scripting through standard Admin methods in CRM
- Extended SDK including Custom Mail Merge, Ajax object, SOAP Object, CRM Date functions etc.