Configuring DataServer to support remote clients

Posted by jamali on 27-May-2016 07:59

I have been following a (somewhat outdated?) tutorial to get access from our UNIX system to an SQL database on this server.

It seems the instructions in the tutorial do not cover setting up a UNIFIED broker that will always remain available.

So far, I have:

1. created an SQL database (BarcodeHQ) with information that I need to access/test

2. created a system DSN with the default database being BarcodeHQ (named it myDSN)

3. Configured a schema holder (mySchemaHolder), using the tables I need from the database in step 1

From here, the instructions seem to show how to configure the DataServer Broker, but the DBA who was helping us out did not follow this (since the broker session would die once the terminal was closed). He instead set up a unified broker (mssbroker1). Unfortunately I didn't follow along very well...

So my next questions would be:

1. Do we need to set up a new broker for the new schema we created, or can we use the same unified broker? If so, how do I check the status of that unified broker? 

2. What are my next steps to set this up (how do I service the broker to accept remote connections?)?

3. We'll be connecting directly from within a program on the UNIX box, using the "CONNECT " command, so given our DSN, schemaholder and broker names, what will our connection string be?

I may need more details than the average poster, as I'm unfamiliar with the dba side of things (I'm more heavily involved in development within a nice safe (and previously configured) environment).


All Replies

Posted by Rob Debbage on 31-May-2016 05:45

Hello Jamali,

Most of the details that you need are in the KB article that you reference. I see that it also reference the product manual, which is available here:

To answer your questions,

1) No. The DataServer broker is an independent module which can be used with any schema holder of the appropriate type. However, you may wish to create additional brokers in order to keep things separate.

2) As a starting point, start the default instance (MSSBROKER1) in Progress / OpenEdge Explorer. That's essentially it.

3) Here are a couple of sample connection strings modified from the KB article showing a) how to connect to the DataServer Unified broker via the NameServer and b) how to connect directly to the Unified Broker.

/* Connect via NameServer - where 5162 is the default port for NS1 */

_progres holder -H hostname -S dbservice -N tcp -db dsn_name -dt MSS -ld logical-datasrc-name -H hostname -S 5162 -N tcp -U userID -P password -Dsrv svub,1 -DataService mssbroker1

/* Direct connection to DataServer broker - where 4446 is the default port for MSSBROKER1 */

_progres holder -H hostname -S dbservice -N tcp -db dsn_name -dt MSS -ld logical-datasrc-name -H hostname -S 4446 -N tcp -U userID -P password -Dsrv svub,1

These can be split into 2 separate CONNECT statements (1x schema holder, 1x MSS database), e.g.

CONNECT holder -H hostname -S dbservice -N tcp.

CONNECT -db dsn_name -dt MSS -ld logical-datasrc-name -H hostname -S 4446 -N tcp -U userID -P password -Dsrv svub,1.

Kind regards,


This thread is closed