Related Links:
ccmMX ccmMercury Exchange Service – Share ccmMercury data between organizations
ccmMX is comprised of two services which manage the transfer of records and attached documents between two ccmMercury databases.
ccmMX enables different organizations with ccmMercury databases to share work. The two organizations need not have the same version of ccmMercury, nor the same screen layouts or databases.
The organizations' functional representatives and system administrators, along with WorkDynamics Analysts, will determine the business rules to apply when sending new records or updating them, including what to send and when.
Key Benefits
- Avoid Duplicate Entry
Many organizations currently enter data into their database then mail or e-mail the item to another department or agency who re-enters much of the same information into their own ccmMercury database. The use of ccmMX will eliminate this duplication of effort. - Faster Turnaround Times
Handling items electronically eliminates the time and effort wasted re-entering, mailing, e-mailing and calling. - Improve Business Process
Automating the transfer of information as well as when it will occur will ensure that your organizations' processes are followed. - More Accurate Data
Transferring the core information as well as any desired comments or documents, etc. ensures that the other organization has the vital information in their ccmMercury record -- human error has been reduced.
Key Features
- ccmMercury Exchange web-service
This is a .NET based web-service that supports industry standard web-service protocols (SOAP, WSDL, and MTOM). It is responsible for receiving record exchange requests from the sender and updating the local ccmMercury database. The web-service uses the ccmMercuryPlugin.dll COM library to populate the ccmMercury database. This plug-in will ensure that all CCM Account Manager business rules are processed including default values, data entry restrictions, validations, and e-mail notifications. - ccmMercury Exchange client service
The client service is a .NET based Windows service that is responsible for sending records to the receiving client’s web-service. It does this by monitoring the EXCHANGE_RECORDS table in the ccmMercury database for pending records. The service will then retrieve the record data from the ccmMercury database along with any file attachments (including DM document files) and call the receiving organization’s ccmMercury Exchange web-service. The web-service will send back a response indicating whether the exchange was successful. The client service will update the EXCHANGE_RECORDS table in the ccmMercury database indicating whether the transfer was successful. - Send and retrieve data across differing databases
Typically, organizations that want to share data will not have the exact same ccmMercury screen, nor the same business rules. ccmMX allows organizations to map fields between the two databases to meet the needs of both organizations. It is possible to define what data is sent and when (first time, always, when something is true, etc.) to fit each organization's requirements. - Document Management
ccmMXallows organizations to send and/or receive ccmMercury attachments, or DM attachments. Each organization can decide independantly whether to use versioning or add new documents each time. Business rules will determine the implementation.
System Dependencies
- Windows 2003 Server
- Internet Information Server (IIS) Version 6.0
- SMTP
- Microsoft .NET 2.0 framework
- Microsoft web-service enhancements 3.0 runtime (MTOM and security token support). This component is installed as part of our setup.