Publisher Deep Dive

33

Abstract

All of the Application Adapters have associated publishers which generate XML in the MSMQ. And because each one works a bit differently we will discuss the entities, Windows Services, customizations, and message queues that operate to transport messages from applications into the Microsoft Message Queue. Before this session is complete you will have a full understanding of how to troubleshoot and optimize the integration by detailing how XML gets generated for each publisher type.

4

Agenda

Overview of Publishers

Types of Publishers

Details of how each publisher works

Troubleshooting

Tips n Tricks

55

Overview

Publishers provide Event Driven integration from specific apps

Utilize outbound capabilities

Each one is different

Allows real time integration capabilities

Data flows to PubIn then to ScribeIn

66

Application Publishers

CRM GP AX NAV

SFDCEmail Bridge

Query

7

Publisher Details

Dynamics CRM

•CRM Plugin

•CRM Workflow

•Custom Object?

Salesforce.com

•Outbound Message

• IIS ASP page

8

Publisher Details

Dynamics GP

• SQL Triggers

• Shadow Table

Dynamics NAV

• Codeunit Changes

• PubQueue Table

Dynamics AX

• Codeunit Changes

• PubQueue Table

CRM PublisherSc

rib

e Se

rvic

esC

RMM

SMQ

DTS

Phase

Update / Insert / Delete Plugin

Tracking Token

Bridge

XMLTemp

Bridge Filter

XML Scribe InQueue

Listener

Message Processor

SFDC Publisher

Scri

be

Serv

ices

SFD

CM

SMQ

DTS

Web

Pag

e

Phase

Update / Insert / Delete Plugin

Outbound Message

XML Scribe InQueue

Listener

Message Processor

ASP Page

GP PublisherSc

rib

e Se

rvic

esG

P SQ

LM

SMQ

DTS

Phase

Update / Insert / Delete Trigger

Shadow Table Update

Bridge

XML Scribe InQueue

Listener

Message Processor

AX PublisherSc

rib

e Se

rvic

esA

XM

SMQ

DTS

Phase

Update / Insert / Delete Document Services

PubQueue TableScribe Service Filter

XML Scribe InQueue

Listener

Message Processor

NAV Publisher

Scri

be

Serv

ices

NA

VM

SMQ

DTS

Phase

Update / Insert / Delete NAV

Custom Code

PubQueue Table

Bridge

Filter

XML Scribe InQueue

Listener

Message Processor

XML Scribe InQueue

Bridge

1414

MSMQ Points of Interest

XML Messages can only be 4 MB (Not Characters) in Size

• Typical XML message is 75k (2 Million Messages = 150 MB)

• Attachments are uncompressed in an XML document

Durable and Transient Message Queues

ALL Messages in Queue Reside in Server RAM Pool

1515

MSMQ Trouble Shooting

"Insufficient Resources"

• The message size is too large

• The machine quota has been exceeded

• Routing problems when opening a transactional foreign queue

• Lack of disk space

1616

Troubleshooting

Use PubSucceeded

Test queue security

• MSMQ test tool in Scribe install

Check queue storage limits

• System DeadLetterMessages

Look at the originating app for errors

1717

Tips and Tricks

Use Joins in XMLUtilize Filtering to

reduce noise

Leverage queue forwarding inside

the integration processes

Utilize DTS parameters for

routing