Skip to main content

OMACONFIG XML file in SAS

In this article you can get information about OMACONIFG.xml file and how to set email alert using the option available in OMACONFIG.xml file.

  • File location: SAS-configuration-directory/Lev1/SASMeta/MetadataServer
  • Restart required: Yes, if changes are made to this file Metadata Server should be restarted for the change to take effect. 

During metadata server start-up, omaconfig.xml file is read. Metadata server reads omaconfig.xml file to get the path of repository manager. It also have information like journaling options, library used by repository manager, internal users password policy and email alert emails.

There are several other options that can be defined in OMACONFIG xml file, however, following tasks will be done frequently in OMACONFIG xml file.

Frequent task in OMACONFIG xml file done by SAS Admin

Provide ability to store credentials in a connection profile

Connection profile is used by SAS desktop application like SAS Enterprise Guide to store user ID and password. Below is the image of connection profile window.



In omaconfig.xml file, SASSEC_LOCAL_PW_SAVE option is used is to set the ability to store credentials in a profile.

  • If SASSEC_LOCAL_PW_SAVE=1, the users can save their user ID and password in the connection profile. 
  • If SASSEC_LOCAL_PW_SAVE=0, the users cannot save their user ID and password in the connection profile. 


Configure alert e-emails:

Metadata Server will generate alert email whenever there is a downtime. The email will be sent to the email addresses specified in the OMA ALERTEMAIL option in the omaconfig.xml file. The subject of the alert email will be Metadata Server Alert and body of the alert email will be error message, host machine of the metadata server and the  metadata server log path.

The automatic email will be triggered in the following situations:

  • Metadata server backup or recovery errors
  • Any issue while journal updates the repository data 

You can test the alert mail using SAS Management Console Metadata Manager plug-in. In Metadata Manager plug-in, right-click Active Server and select Properties. There you will find Send Test Message. Clicking on it will open Send Alert Email Message dialog box. Enter the contents to be displayed in email and click OK.

Changing journaling option

You can change the journaling type to NONE or SINGLE or ROLL_FORWARD in JOURNALTYPE option.

XML elements in omaconfig file

The file contains three XML elements OMA, RPOSMGR and Internal Authentication Policy.

<OMA>
It is used to specify any option related to metadata server. The examples that I have explained above will be under this element.

<RPOSMGR>
It is used to specify any option related to repository manager. Example: LIBREF, ENGINE, PATH etc option. These option is used to specify LIBREF, ENGINE, PATH of repository manager.

<InternalAuthenticationPolicy>
Options in this xml tag includes ChangeDelayInMinutes, ExpirationDays, ExpirePasswordOnReset etc. All the options enclosed within this tag is case sensitive.

Comments

Post a Comment

Popular posts from this blog

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

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT.  So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log.  Any suggestions? Answer: Please do the following:    1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop  2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`:  if [ -n ""$TKPATH"" ]; then  unset TKPATH  fi   if [ -n ""$TK_PATHLIST"" ]; then  unset TK_PATHLIST  fi    3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start  The above code change in ObjectSpawner.sh should fix the issue.
1 comment
Read more

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...
3 comments
Read more