09-17-2014 06:09 AM
1. I am trying to set up Model Manager 12.1 (sas9.3). When trying to launch the application via Web Start http://hostnamet:8080/SASModelManagerJWS/Status (I am using actual hostname here). I am getting the following error:
My Web Start Settings:
However the http://hostname:8080/SASLogon/sas-environment.xml is accessible via browser.
The script of the environment file:
<environments xmlns="http://www.sas.com/xml/schema/sas-environments-9.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sas.com/xml/schema/sas-environments-9.2 http://www.sas.com/xml/schema/sas-environments-9.2/sas-environments-9.2.xsd ">
2. When I am trying to open the software with the client application (on Windows) I get the following error:
The log of the error is attached.
The log says:
java.lang.RuntimeException: java.lang.RuntimeException: com.sas.analytics.modelmanager.core.AuthorizationException: The application could not connect to the SAS Metadata Repository "dav://budsas20.finalyse.group:8080/SASContentServer/repository/default/ModelManager".
Make sure that the SAS Content Server is available, and that the user is a member of a SAS Model Manager group.
I have validated the Content Server via Management Console. The user I am using is in the Model Manager Administrator group (actually I added my user to all the MM groups and roles via Management Console)
The ModelManager.ini configuration file for the windows application is the following:
And the sassw.config file is the following:
JREHOME=C:\Program Files (x86)\Java\jre1.6.0_24\bin\java.exe
Do you have any ideas what might be the problem?
09-18-2014 04:19 AM
I made the notice as your are using both names. I do not expect the name hostname is valid hostname. It shows in the model manager checkpage and not your name localhost.
09-18-2014 04:31 AM
Thank you for considering this question. In terms of the Windows client the problem was with post configuration of Model Manager. The action that was missing:
since I selected to not automatically deploy the SAS Web Applications, manual steps were required to ensure the proper content is loaded to the SAS Content Server. The file, .../Lev1/Web/Utilities/manualLoadContent.sh, has been created to facilitate this process. I had to run the file and modify sas sassw file in the client folder.
Still can not access Model Manager via a web application. The error message with the inability to find the environment file even though I added path to environment file in the Management Console.