I stumbled across this problem after removing a Document Type in Designer without removing the corresponding Document Type on the Broker and then creating a new Document Type with the same name as the previous one. In this case the Broker will create a new Document Type with the extension “_1” and all changes will sync to this one instead.

Example:

1. Delete a Publishable Document Type eg ‘myDocument’ using the Designer (without removing it from Broker)
2. Now create a new Document Type called ‘myDocument’ and make it publishable
3. If you now check the Broker Doc Type in the properties you will see that its name is wm::is::myDocument_1

To fix this we have to go through a number of steps:

1. Open MWS->Messaging->Client Groups and click ‘IntegrationServer‘
2. Open tab canPublish and use next to find ‘myDocument‘ and ‘myDocument_1‘
3. Tick the box to the left of both Document Types and then click ‘Delete‘
4. Open canSubscribe tab and use next to find ‘myDocument‘ and ‘myDocument_1‘
5. Tick the box to the left of both Document Types and then click ‘Delete‘
6. Now go to MWS->Messaging->Message Types
7. Use ‘Next‘ to find both the ‘myDocument‘ and ‘myDocument_1‘
8. Tick the box to the left of both Document Types and then click ‘Delete‘
9. Now go into Designer and find the ‘myDocument‘ Document Type and lock it for edit
10. In the properties section temporarily change ‘Publishable‘ to ‘false‘ and save
11. Now change the ‘Publishable‘ property back to ‘true‘ and save

The doctype should now be called ‘myDocument‘ on the Broker and it should also be found in canPublish and canSubscribe on the ‘IntegrationServer‘ Client Group. It is quite a lot of steps to fix this error. To never have to face this situation again be sure to ALWAYS delete the publishable document on the Broker if you remove it in Designer

NOTE! When this happens there is also a possibility that you have to reset the triggers that use this Document type – that has happened to me a few times. Just delete the Document Typer on the trigger and add it back (and set the appropriate filters again) and it should start working again

Tested on webMethods IS 8.2.2