Posted by Bill Goulette on Thu, May 27, 2010
When we started integrating systems with Boomi, the key to our relationship with them was the ability to offer a hosted integration solution that would work with the two CRM applications that we consult on: Microsoft Dynamics CRM and Salesforce CRM. Boomi now offers integration adapters for both Salesforce and Dynamics CRM -- the Dynamics CRM solution being a fairly recent addition to their offering. Their Dynamics CRM adapter works for both the on-premise and on-demand versions offered by Microsoft. They still offer connections to key financial packages like Peachtree, QuickBooks, MAS 90/200/500 and Dynamics GP as well as the larger enterprise systems like Oracle, PeopleSoft and SAP.
Posted by Bill Goulette on Tue, Mar 09, 2010
Scribe Insight DTS packages, which are the integration mappings and instructions component of a Scribe integration, may be scheduled and managed through a tool called the Scribe Console.
The tool presents categories of information in a tree on the left side and list views on the right. The list views within the Collaborations - Integrations area of that tool provides an overview and general status of the scheduled integrations. Occassionally, the status might give you something other than the designed Paused or Active status. When the status is Failed, the desciption column will give you some information on the reason.
I recently encoutered an error I hadn't seen before that I couldn't readily find the answer for:
"The Job was terminated because the message processor is unresponsive."
After some research it was discovered that there is a 60 second timeout built into Scribe that is applied to the time the source query is initially executed and the time that the first row is processed into the target. There are a variety of reasons for why this might happen (server latency, network latency, etc...). While you are trying to determine the cause for the latency, there is a registry entry you can create that will allow for a manual override of the standard timeout.
The key named ProcHangTimeOut needs to be created in the HKEY_LOCAL_MACHINE\SOFTWARE\Scribe\EventManager\Settings key. This represents the timeout in seconds. Set this to what makes sense for you.
Remember that messing around in the registry is inherently dangerous if you don't know what you are doing, so be careful not to disturb anything else when working in the registry.
Posted by Bill Goulette on Mon, Mar 01, 2010
As part of our integration practice, we end up creating integrations that are well outside the functionality of templates offered by the integration software provider. In particular, there are times where the tables involved in the integration need special inclusion in the security model that informs the integration module.
Each integration software has different methods for providing object access to the integration tool. In Scirbe Insight's case, when it comes to Dynamics GP, the list of SQL objects that can be accessed by their tool is contained in a table called KSYNCTABLEBASE located in the company database (not to be confused with the DYNAMICS database).
It is likely that part of your design document includes identification of the objects that are being integrated between the systems. You can check to see if the tables included in your integration design are accessible by reviewing the results of the following query against the company database:
select * from KSYNCTABLESBASE
Note - of course, you must have Scribe Insight and the Scribe GP Adapter installed for this table to exist there.
If the table you are looking for is not found there, you may add it using the following query and substituting the 'PA00401' value with whatever table you need to access with the Scribe Workbench:
INSERT INTO KSYNCTABLESBASE
( TABLENAME, OWNER, SUBJECT_AREA, LABEL, TYPE, UPDATABLE, HIDDEN, DRS_OBJECT, BASE_TABLES, REMARKS, FIELD_INFO )
VALUES
( 'PA00401', 'dbo', 'Additional Integration Objects', null, 'U', 'Y', 'N', null, null, 'Table used for additional information', null)
Happy integrating.