topic Re: Problem of Deploy Enterprise Miner 7.1 with JBoss in Administration and Deployment

Problem of Deploy Enterprise Miner 7.1 with JBoss

Slash — Wed, 13 Apr 2016 05:58:01 GMT

Hi ,guys.

I was deploying EM on Windows Server with standard plan "Enterprise Miner, one machine, JBoss". There is no error or warning in the whole installation and configuration.

When finished, Open the Enterprise Miner Mid-Tier Status URL:"http://bmjs_fs_sas01:8080/SASEnterpriseMinerJWS/Status" successfully. Then click the Start, start EM Client, input sasdemo user and password, and cannot log. It said "The Environment URL is invalid".

And I type the Environment URL "http://bmjs_fs_sas01:8080/SASLogon/sas-environment.xml" in the browser, an error occurred.

HTTP Status 500-

type: Exception report

message:

description: The server encountered an internal error () that prevented it from fulfilling this request. exception:

java.lang.IllegalStateException: Unable to retrieve a theme object given this cascade of names available. Please verify your configuration;

......

The detail message is in the pic below.

What's then possible reason?

Re: Problem of Deploy Enterprise Miner 7.1 with JBoss

PaulHomes — Wed, 13 Apr 2016 06:10:03 GMT

Have a look at SAS Installation Note 36547: A host name that includes an underscore or other unreserved characters causes problems for SAS® Business Intelligence Web applications. I can see the URL that you posted has underscores in the host name and so I imagine this way be the cause. According to the RFCs underscores shouldn't be used in host names.

Re: Problem of Deploy Enterprise Miner 7.1 with JBoss

Slash — Wed, 13 Apr 2016 06:50:39 GMT

Thanks, It seems that's the reason. Let me test it.
Thanks again.

Re: Problem of Deploy Enterprise Miner 7.1 with JBoss

Slash — Wed, 13 Apr 2016 08:56:38 GMT

Thanks, that's the reason. I thought it's the JBoss, so I've tried different version for a long time. I should ask you guys early.

Re: Problem of Deploy Enterprise Miner 7.1 with JBoss

PaulHomes — Wed, 13 Apr 2016 10:16:03 GMT

No problem. It reminded me of a short blog post I wrote about it back in 2010.

It's good to hear you were able to resolve the issue. Thanks for taking the time to mark it solved too.