Open topic with navigation

Setting Up The Publisher Process And Queues

If needed, set up a publisher process in the Console and create the publisher message queues.

Note: If you already have a working Publisher for Dynamics NAV, you can skip this task.

The Publisher for Dynamics NAV is included as part of the TIBCO Scribe® Insight installation. For more information, see the TIBCO™ eDelivery site.

To create a publisher in the Console

1. In the Console, expand the Integration Server node and click Publishers and Bridges.
2. Click Add.
3. In Step 1Publisher/Bridge Type, select Microsoft Dynamics NAV for Publisher /Bridge type.

4. Define a name for the publisher in the Name box. The Creator and Server boxes are populated automatically.
5. Click Step 4 Publisher/Bridge Properties. The Publisher for Microsoft Dynamics NAV window is displayed.
6. Enter the connection information for your Microsoft Dynamics NAV server:

   Dynamics NAV 2013 And Higher Connection Settings

   

   • Dynamics NAV 2009R2 — Disable this check box for Dynamics NAV versions 2013 and higher.
   • Server Name — Name of the Database server.
   • NAS Server Name — Name of the computer where NAS is installed, followed by the port number if needed.

     Note: The default port number is 8085. If your company uses the default port, you do not need to specify the port number.
     
     If you are using a different port number, you must specify it. For example NAVTEST:8003. For more information about setting up the NAS service and specifying the port, see Supporting Multiple Organizations.

   • Company — Name of Dynamics NAV company. This field is case-sensitive.
   • User ID — Name of user or login name.
   • Password — User's password.

   Dynamics NAV 2009 R2 Connection Settings

   

   • Dynamics NAV 2009R2 — Enable this check box only if your Dynamics NAV version is 2009 R2.
   • Server Type — Type of server you are using.
   • Server Name — Name of the Database server.
   • NAS Server Name — Name of the computer where NAS is installed, followed by the port number if needed.

     Note: The default port number is 8085. If your company uses the default port, you do not need to specify the port number.
     
     If you are using a different port number, you must specify it. For example NAVTEST:8003. For more information about setting up the NAS service and specifying the port, see Supporting Multiple Organizations.

   • Database Name — Name of database.
   • Company — Name of Dynamics NAV company. This field is case-sensitive.
   • Authentication — Type of authentication you are using.
   • User ID — Name of user or login name. For Windows authentication include the domain, such as domain\Username or Username@domain.com.
   • Password — User's password.

   When creating the publisher, three publisher message queues are created on your Insight server. The queue names use this format: SCRIBESERVERNAME\Private$\NAVSERVERNAME_MSNAVPubIn.

   When creating the publisher, three publisher message queues are created on your Insight server. The queue names use this format: SCRIBESERVERNAME\Private$\NAVSERVERNAME_MSNAVPubIn.

   For example, MYSCRIBESERVER\Private$\MYNAVSERVER_MSNAVPubIn.

7. Click the MSMQ button, and select the Log messages that were forwarded to ScribeIn, ignored or filtered option.

   Note: TIBCO recommends selecting this option while you are setting up the publisher to assist with troubleshooting. Clear this setting after verifying that the publisher is set up and working properly.

8. Click OK.
9. If you need to review the connection information, click Settings in Step 4 Publisher/Bridge Properties.
10. Click Step 5 Activation, and click Active.
11. Click Finish.

Troubleshooting Schema Errors

If the following error message appears when you try to create a DTS with an XML connection, your XDR schema has duplicate node names: Invalid Schema or Document: Node list not unique.

When you create a schema using the Publisher for Dynamics NAV, Insight generates a schema file in .XDR format. The XDR schema is created with a node for Entity, Parent Object, and Child Object, even if the entities or objects use the same name, such as an Account Entity and an Account Child Object.  

Although the publisher creates a schema with identical nodes, XDR schema standards prevent the Workbench from opening or processing it. To work around this issue, use an XML sample message as the schema. Create an XML sample message: 

• In the Console, add a new publisher as described above.
• Perform an action in the Adapter for Dynamics NAV, such as an Update or an Insert, that causes a message to be published to the ScribeIn queue.
• Save this XML message and use it as both the sample file and the schema when creating the DTS. 

See also

Configuring The Publisher

TIBCO Scribe® Insight Help Library