Unable to integrate the SAS server in client app using username and password

[mkraman85]

We are trying to build the client application using the SAS integration technologies based on the links mentioned below:

https://communities.sas.com/t5/SAS-Communities-Library/Create-your-own-client-apps-using-SAS-Integra...

For this, we are referring the .net based “SAS program harness” tool with our application where we could connect the SAS server using the “SAS Workspace Server” with COM connection protocol, but we could not connect the SAS server using the user name and password.

We also tried to test the SAS connection through the "SAS Integration Technologies Configuration Wizard".  But we are getting an error.

Below options were used in integration technologies (used different connection protocols like COM, DCOM, IOM Bridge)

1. SAS Workspace Server
2. SAS Metadata Server

[ChrisHemedinger]

Can you provide more details about the error, and also the SAS environment you're trying to connect to? If the IT Config app doesn't work with the connection, then the custom client app (which uses the same mechanism) won't work either. Can you connect using a SAS application like SAS Enterprise Guide?

BTW, the COM method supports only local installed SAS, and no credentials (uses same user as logged in). Only the IOM method supports credentials, but you need an object spawner with a listening port to connect to.

[mkraman85]

SAS Environment : Base SAS 9.4

How to verify the "object spawner" is running on the SAS server?

For now, we are using the COM method, since we are not able to pass the credentials (username and password) using IOM bridge.

Getting the below error, when I click on "Test" in the "Integration technologies Configuration" wizard

[ChrisHemedinger]

The IT Config tool can test either a metadata server connection (default port 8561) or a Workspace server (default port 8591). Note that the ports configured may be changed by an admin who set these up.

If you just want to see whether a port is open and listening on a remote machine you can use the Test-NetConnection PowerShell command on Windows (it's like ping, but with a port specified).

 Test-NetConnection -ComputerName myserverhost.company.com -Port 8591

ComputerName     : myserverhost.company.com
RemoteAddress    : 10.xx.nnn.nnnn
RemotePort       : 8591
InterfaceAlias   : Ethernet
SourceAddress    : 10.nn.yyy.zzzz
TcpTestSucceeded : True

[mkraman85]

Below was the response from powershell command.

Test-NetConnection -ComputerName *****123.*****.com -Port 8591

WARNING: TCP connect to (10.xx.nnn.nnnn : 8591) failed

ComputerName : *****123.*****.com
RemoteAddress : 10.xx.nnn.nnnn
RemotePort : 8591
InterfaceAlias : ******************
SourceAddress : 10.xx.nnn.nnnn
PingSucceeded : True
PingReplyDetails (RTT) : 258 ms
TcpTestSucceeded : False

Does it require a separate license for workspace server to run on the default port 8591?, will it not be available in the base SAS 9.4?

[andreas_lds]

---

@mkraman85 wrote:
...

Does it require a separate license for workspace server to run on the default port 8591?, will it not be available in the base SAS 9.4?

---

As far as i know, a bi-server licence is required.

[ChrisHemedinger]

To have a SAS environment ready to accept connections on a remote server, it must be configured using SAS Integration Technologies (a product included in the BI Server bundle, as was mentioned earlier).

Usually there would be a metadata server (to function as a directory of available servers, libraries, and user permissions), an object spawner (a daemon that runs listening for connections and will launch a SAS session as needed), and eventually a Workspace server (the SAS session that is launched by the object spawner).

To support connections from a client machine to a remote machine with SAS, you would need this additional license for SAS Int Tech and the configuration.

[Kurt_Bremser]

8561 is the port used by the metadata server, the workspace server protocol won't work there.

Use SAS Management Console to connect to 8561 on the metadata server, then validate the application servers from there.