R
Rob Debbage
Guest
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: documentation.progress.com/.../dmsql.pdf 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, Rob
Continue reading...
Continue reading...