Leave feedback
  • Archiving from StreamServe to Content Server using Enterprise Library Services

Write an Article
Thursday 04 October, 2012
Dave Lahn Dave Lahn OpenText Employee
6 likes 5190 views

One of the neat features added in EP1 is the ability to archive documents from StreamServe into Content Server by means of Enterprise Library Services (ELS).

This guide will run through a very basic example of how to set up this functionality. I can provide an example project upon request.

This guide assumes that you have a working StreamServe SP5 EP1 installation, Enterprise Library Services with Content Server, and the Open Text Administration Client.

I've also attached a PDF of this article, which has clearer screenshots.

For this example, a basic invoicing project will be used. We will be archiving invoices with the following metadata: InvoiceID, CustomerID, CustomerName, and InvoiceTotal.

Defining the Application and Document Model in Enterprise Library Services

The first step in this process is to define our document in Enterprise Library Services. In order to do this, we will have to create an Application that StreamServe will interface with.

1)      Under the Enterprise Library Services node in the Open Text Administration Client, right-click Applications and select New Application.

2)      Fill in an Application name and password as shown below. For the purpose of this example, I called my application StreamServe.


3)      Now we want to create a Document Model. Right-click the Document Model node and select New Item Type.

4)      Fill in the Item Type Name as shown below.  For this example, I called it strs.Invoice. All of the other fields can be left as the default for now. Select Next, Next, and then Finish.


5)      The next step is to add our metadata to this new document model that we’ve created. In the Document Model node, select strs.Invoice, and on the right side, select Assign Property Type.

6)      Specify InvoiceID for the Property type name, select the Searchable checkbox, and click OK.


7)      Repeat Step 6 for CustomerID, CustomerName, and InvoiceTotal.

Our document is now defined in Enterprise Library Services. At this point, we can close the Open Text Administration Client. It is now time to configure our StreamServe project to interact with Enterprise Library Services.

Configuring a StreamServe Project to Archive to Content Server

Most of the following information is also available on page 195 of the EP1 Reference Guide, however, I will re-iterate some of it here for the sake of this guide. If you’d like more in-depth information regarding different ways to configure your project, and the pre-defined metadata, please refer to the reference guide.

There are two ways to use a StreamServe project to archive documents into Content Server; an ELS Archive Filter, or an Archiver application. In this guide, I will be discussing the use of the ELS Archive Filter. For further discussion on the difference between the two methods, please refer to the reference guide.

1)      First, we want to create a corresponding document type for the strs.Invoice document model we defined in ELS. In your StreamServe project, create a new document type and call it strs.Invoice.

2)      We must load in the pre-defined metadata that ELS will require for archiving. This is provided in the StreamServe SP5 EP1 installation in <StreamServe installation directory>\Applications\StreamServer\5.5.0\Tools\System\data\dcres\ELSSytemMetadataGroup.dcres. Import this file into your resource set as a Metadata Group.

3)      Open up the new ELSSystemMetadataGroup Metadata Group created, and select the Share button. Share this with the strs.Invoice document type as shown below.


4)      Create a new Metadata Group in your resource set called Invoice, and open it up.

5)      As we did in Step 3, share this Metadata Group with the strs.Invoice document type.

6)      As we did in ELS, we will have to add the various metadata that we are going to store. Select the Add (+) button and add InvoiceID, CustomerID, CustomerName, and InvoiceTotal to the metadata group.


7)      Now we want to map the appropriate variables to the metadata in our document type. Open up the strs.Invoice document type in your resource set.

8)      For each of the metadata in Invoice, I have set them to Variable and mapped them to the variables specified in my XMLIn event. You can specify these however you’d like. Make sure that each of these has Archive set to Yes.


9)      In order for this to work, you will also have to specify queues on both your input and output connectors. For further information on how to do this, please refer to the Design Center documentation.

10)   In the runtime settings of your output connector, select the Archiving tab in the appropriate section. As my project is outputting in Document Mode, I have selected Document End.

11)   Set the Document Type to strs.Invoice from the resource set, and click OK.


12)   It is now time to add our ELS Archive Filter. In your resource set, create a new Filter Chain called ELS, and open it up.

13)   Under the Filter Chain menu, select Add Filter, and then ELS Archive Filter.

14)   You now have the ability to specify some information that will tell ELS how and where to store the documents in Content Server. For this example, I have specified my ELS Folder ID (which can be obtained from Content Server), the Document name, which I have set as a variable in a script in my project, and Allow Multiple Versions. Once again, these things can be specified in a few different places, so please refer to the reference guide for detailed information.


15)   In your output connector, add the ELS filter chain.


16)   Export and deploy your application in Control Center.

Mapping the StreamServe Metadata to ELS

There are a few ways to do this, so please review the reference guide. In this example, I will be using the ELS Mapping Tool. It is located in <StreamServe installation directory>\Applications\Management\5.5.0\bin\

1)      Copy the elsmaptool.ini file into the working directory of your project.

2)      Edit this file to match your ELS configuration.


3)      From the working directory of your application, run the elsmaptool.exe file from a command prompt, located at <StreamServe installation directory>\Applications\Management\5.5.0\bin\elsmaptool.exe

4)      The above step created a file called strselsmetadatamap.xml. The metadata and document types have now been mapped to ELS from StreamServe.

Adding a Connection to ELS in Control Center

1)      In Control Center, until the Repositories node, right-click and select New ELS Archive.

2)      Select a name for the archive, and select OK.


3)      Fill in the appropriate configuration for your ELS environment when asked, and select OK.


4)      Now link the ELSArchive we created to your application domain by right-clicking and selecting Link Application Domain. From here, you can select your application domain from the list.

Your application should now be set up to archive to Content Server through ELS. If everything is configured directly, when you run an input file through, your documents should go to the folder you specified in Content Server.

Happy Archiving!

Attached files

Comments (3)

  • Thanks Dave. This is one of the most well written articles to date here on StreamShare. One thing to mention is that we have now created a metadata mapping tool where you can map existing metadata visually. The best feature is however that you can export a StreamServe document type as an ELS document type and then import it to Content Server and vise versa. That simplifies metadata mapping a lot. This tool arrives in StreamServe 5.6. 

    well done!

    Thursday 04 October, 2012 by Stefan Cohen
  • Hello Dave,

    Nice Article. is it possible to send me the sample project for the archiving.

    My mail  ID: satishgaikwad7@gmail.com

    Thanks in Advance.

    Satish gaikwad



    Thursday 26 February, 2015 by Satish G
  • Basic question -  

    Connection profile for Enterprise Library - from Storing Documents in Content Server User guide.

    Creating Archive repository which links to OpenText Arhive is Content Server OR Archive repositoy of OpenText.

    Both are different if I am not wrong.


    Wednesday 17 June, 2015 by Mitesh Kothari


Post comment