Documentum BizTalk Adapter V0.1 (Using the Adapter to send Custom Type Documents)

In the previous post I showed how we can use the adapter to send files to Documentum to be stored as documents of type “dm_document”.

A more practical use for the adapter is to use the adapter to send files to be stored as custom type documents, to do so we need to create a schema that reflects the custom type definition, I employed the adapter metadata wizard, here is a walkthrough on how to use this functionality:

- create a new empty BizTalk project, right click the project in the solution explorer and click add generated item

- The add adapter wizard will open, in the first step select the Dynamic Documentum Adapter

a

- On the next step enter the credentials to connect to Documentum and choose the Docbase

b

- In the next step select the custom type you want to import its schema (here I have a custom type purchaseorder that has the following attributes: ponumber(string), supplier(string), podate(time), items(repeating string) )

c

- click the finish button and the wizard will import the schema of the custom type to your project

d

- if you examined the schema generated by the adapter, you will find four xml elements: the first one is DocumentumName which should contain the name of the document to be saved in Documentum, the second element DocumentExtension should contain the extension of the file to be uploaded to Documentum, the third element DocumentContent contains the file content in base64Binary format, the fourth element DocumentAttributes is a complex element with sub-elements that correspondences to the custom attributes of the custom type 

e

- To test the adapter I will pass an XML file that matches the schema above, I will set the DocumentContent to be a simple string represented in base64Binary and will upload it to Documentum as a text file(DocumentExtension=”.txt”), of course a better way to do this is to use a custom pipeline component to automatically convert the physical file to its base64Binary but I will leave this to another post

- In the orchestration file created by the add adapter metadata wizard add a receive port that receives xml files from a certain folder

g

- add another port to send to Documentum, when prompted for the adapter type choose the existing adapter type SubmitpurchaseorderPortType this port type correspondences to the schema described earlier, set the communication direction to send request and receive response, specify the binding later

f

- The response returned from the Documentum adapter contains the r_object_id on the new document sent to Documentum, I will take this response and send it to a specific folder using a simple FILE send adapter, so my orchestration will look like the following

h

- Deploy the orchestration and go to the BizTalk Admin Console to configure it, choose BizTalkServerApplication as a host, and for the outbound logical port “SendToDocumentumPort” choose to create a new send port

i

- In the new send port properties window, choose the BizTalkServerApplication as the send handler and the XMLTrasmit, XMLReceive for the send and the receive pipelines, configure the adapter and set the adapter specific information (Docbase, username, password, Document path, etc.)

j

- Now start the orchestration and try to place xml file with our schema in the receive folder, go to Documentum to the location you specified in the send adapter configuration you will find a new document of type purchaseorder there that has the Name, file type, content and attributes that is specified in the xml file

Comments

Post a Comment

Popular posts from this blog

Documentum DQL Query Custom Data Extension For SQL Server Reporting Services

When it comes to Reporting SQL Reporting Services is my favorite choice. SQL Reporting Services has a plenty of data source types but unfortunately Documentum is not one of them, whenever we have to develop some reports based on the data in Documentum we first develop a web service that contains the necessary DQL queries and returns the result in a Data Set, then we create an XML data source that consumes this web service and use it in our reports. Fortunately SQL Reporting Services allows you to extend its data access capabilities by developing a custom data extension (CDE)that retrieves data from your custom data source. I developed a Custom Data Extension for Documentum that allows you to specify a Documentum Repository as a data source and provide your DQL query that will populate your report, I used the Reporting Services SDK Sample (FsiDataExtension) and this Article as starting points You can download the extension from here To install the extension: you have to install the ex...
Read more

Silverlight 4.0 Tutorial (12 of N): Collecting Attendees Feedback using Windows Phone 7

Image
You can find a list of the previous tutorial posts here Continuing our RegistrationBooth Application… It’s very important to collect the attendees feedback to help us improve the future sessions/events we might organize, we can go ahead and implement this functionality in the RegistrationBooth application. but in this post we will take a different approach, we will implement a Windows Phone 7 application that attendees can use on their phones to submit their feedback. Luckily for us Windows Phone 7 uses Silverlight as its development platform (along with XNA), the Silverlight version on Windows Phone is not the same one as the desktop version, think of this as a compact version that fits the phone capabilities. Before we start creating the phone application, first let’s think how we will bring the data to the phone, in the case of the Silverlight application we used WCF RIA services (DomainService) which provided rich client experience for the Silverlight application, Unfortunate...
Read more

Using taco to create Ionic projects for the Windows platform

Image
Recently Microsoft released Tools for Apache Cordova Command Line Interface (TACO CLI), by using TACO, you can quickly start building awesome Apache Cordova apps really and leave all the plumbing of the different platforms dependencies, plugins, etc. to the tools to take care of. For example the following few commands create a cordova project based on the ionic base template, add the android platform to the project, install the platform requirements, build the app, and run it in the emulator: $ taco create sampleApp --template https://github.com/driftyco/ionic-app-base $ cd sampleApp $ taco platform add android $ taco install-reqs android $ taco build android $ taco emulate android Check the TACO home page of for installation instructions and more information http://taco.tools/ . I ran into a problem when i created a new project based on the ionic base template and tried to run it on a windows 8.1 emulator, to reproduce the issue use the following taco commands to cr...
Read more