Skip to main content

How to connect to SAS Open Metadata Interface

Question:
Below is the code I am using to connect to SAS Open Metadata Interface:

MdFactory factory = new MdFactoryImpl(false);
MdOMRConnection mdOMRConnection = factory.getConnection();
mdOMRConnection.makeOMRConnection(connectionInformation.getHost(), connectionInformation.getPort(), connectionInformation.getUsername(), connectionInformation.getPassword());

I am getting following Exception:
Caused by: com.sas.metadata.remote.MdException: None of the requested encryption algorithms are supported by both peers: AES
  at com.sas.metadata.remote.MdOMRConnectionImpl.makeConnection(MdOMRConnectionImpl.java:1385)
  at com.sas.metadata.remote.MdOMRConnectionImpl.makeOMRConnection(MdOMRConnectionImpl.java:1225)
  at com.sas.metadata.remote.MdOMRConnectionImpl.makeOMRConnection(MdOMRConnectionImpl.java:294)
Caused by: org.omg.CORBA.BAD_PARAM: None of the requested encryption algorithms are supported by both peers: AES  vmcid: 0x0  minor code: 0  completed: No
  at com.sas.iom.orb.brg.Engine.getCrypto(Engine.java:4702)
  at com.sas.iom.orb.brg.Engine0200.flowSendReqs(Engine0200.java:119)
  at com.sas.iom.orb.brg.Engine.flow(Engine.java:698)
  at com.sas.iom.orb.brg.Engine.initClient(Engine.java:660)
  at com.sas.iom.orb.brg.ORBImpl.uri_to_object(ORBImpl.java:119)
  at com.sas.services.connection.ClusterEnvelope.createObject(ClusterEnvelope.java:291)
  at com.sas.services.connection.ClusterEnvelope.getConnection(ClusterEnvelope.java:76)
  at com.sas.services.connection.AggregationKernel.doGetConnection(AggregationKernel.java:242)
  at com.sas.services.connection.ConnectionFactoryKernel.getConnection(ConnectionFactoryKernel.java:325)
  at com.sas.services.connection.ConnectionFactoryShell.getConnection(ConnectionFactoryShell.java:69)
  at com.sas.services.connection.ConnectionFactoryShell.getConnection(ConnectionFactoryShell.java:56)
  at com.sas.services.connection.ConnectionFactory.getConnection(ConnectionFactory.java:71)
  at com.sas.services.connection.ConnectionFactory.getConnection(ConnectionFactory.java:46)
  at com.sas.metadata.remote.MdOMRConnectionImpl.makeConnection(MdOMRConnectionImpl.java:1380)
  ... 11 more

Answer:
In the first line it says about encrption algorithm.
You need the SAS/SECURE jars on your classpath - sas.rutil.jar and sastpj.rutil.jar

Comments

Post a Comment

Popular posts from this blog

Starting Gemfire in SAS

Gemfire is available in both Compute and Mid. The default port is 41415. If you have many gemfire, you may have port numbers incremented by 1, for example: 41416. Gemfire is located under Web. <SASCONFIG>/Web/gemfire. To Start: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh start To check Status: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh status To stop: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh stop If it doesn;t start check port number is occupied by any other process. lsof -i tcp:41415 If you only have one instance then 41415 will be default. If you have Lev2 then it will be 41416
Post a Comment
Read more

SAS 9.4 server startup order

In Linux / Unix OS we normally use sas.servers to start the services. The script in the background follows an order to start the services. It is important to follow the order to run the services correctly. In this post we can see what is the order to start / stop and to generate the sas.servers script. It is not really required to memorize the order because SAS provide an utility to create the sas.servers script automatically which will start / stop the service in order. Starting order SAS Metadata server Olap server SAS object spawner SAS / SHARE server SAS / connect spawner SAP table server SAP remote services SAS deployment tester server Stopping will be the same in reverse. How to create sas.server script? We can create sas.server script by using generate_boot_script.sh. if you have made any changes to your environment like adding a new server or spawner we can use the script to generate new sas.server. You can use the script even if you have removed the spanner o...
Post a Comment
Read more

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more