Architecting, installing and maintaining your SAS environment

Error occured deploying the standard plan: Enterprise Miner, three Machines, JBoss

Accepted Solution Solved
Reply
Contributor
Posts: 65
Accepted Solution

Error occured deploying the standard plan: Enterprise Miner, three Machines, JBoss

Hi, all


     I have two machines(both are Windows Server 2008 R2). One is already deployed the Standard Plan: "Enterprise Miner, One Machine, JBoss". And now I want to deploy the EM Middle Tier on then other machine, so I have two EM JBoss Servers. Here is the primary step:


Step 1: select the deploy plan.

step1.png


Step 2: select deploy the middle tier.

step2.png


And the error occured here: Stage 3 Configuration.

deploy_error.png


Part of the Error log:


.......................................................................................................

[JPSFolder] The ' characters around the executable and arguments are

[JPSFolder] not part of the command.

[JPSFolder] Output redirected to property: JPSFolder.stdout

[JPSFolder] Java Result: 4

     [echo] 说明: 元数据部署过程开始于 Tue May 01 12:19:11 CST 2012。

     [echo] 说明: The following object did not meet the restriction IsUnique (SAS Foundation Services)

     [echo] 说明: 元数据部署过程结束于 Tue May 01 12:19:12 CST 2012。

     [echo] Return Code: 4

[propertyfile] Updating property file: C:\SAS\EMiner\Lev1\Logs\Configure\jps_config_status.properties

BUILD FAILED

C:\Program Files\SASHome\SASFoundationServices\9.3\Config\jps_config.xml:271: The following error occurred while executing this line:

C:\Program Files\SASHome\SASFoundationServices\9.3\Config\jps_config.xml:1282: The following error occurred while executing this line:

C:\Program Files\SASHome\SASFoundationServices\9.3\Config\jps_config.xml:1250: The following error occurred while executing this line:

C:\Program Files\SASHome\SASDeploymentManager\9.3\products\cfgwizard__93427__prt__xx__sp0__1\Utilities\loadMetadata.xml:350: Metadata deployment failed - C:\Program Files\SASHome\SASFoundationServices\9.3\Config\Deployment\Metadata\JPSFolder.xml

  at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)

  at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:394)

  at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)

  at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

  at java.lang.reflect.Method.invoke(Unknown Source)

  at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)

  at org.apache.tools.ant.Task.perform(Task.java:348)

  at org.apache.tools.ant.Target.execute(Target.java:357)

  at org.apache.tools.ant.Target.performTasks(Target.java:385)

  at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)

  at org.apache.tools.ant.Project.executeTarget(Project.java:1298)

  at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)

  at org.apache.tools.ant.Project.executeTargets(Project.java:1181)

  at org.apache.tools.ant.Main.runBuild(Main.java:698)

  at org.apache.tools.ant.Main.startAnt(Main.java:199)

  at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)

  at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)

.......................................................................................................



The whole Error log, see the Attachment. Tnanks!

Attachment

Accepted Solutions
Solution
‎06-12-2014 07:35 AM
Valued Guide
Posts: 3,208

Re: Error occured deploying the standard plan: Enterprise Miner, three Machines, JBoss

Two EM jboss servers???  That are two captains managing your dinghy......

You are missing the fundamental concepts how a sas bi environment is working.

Splitting up the metadata server, midterm (java appserver) and the sas appservers (note the difference in appservers) with a connected dependent desktop (java virtual machine bases) is all nice. But you must know all requirements and relationships. It is not the kiddy approach of type setup enter.

---->-- ja karman --<-----

View solution in original post


All Replies
Solution
‎06-12-2014 07:35 AM
Valued Guide
Posts: 3,208

Re: Error occured deploying the standard plan: Enterprise Miner, three Machines, JBoss

Two EM jboss servers???  That are two captains managing your dinghy......

You are missing the fundamental concepts how a sas bi environment is working.

Splitting up the metadata server, midterm (java appserver) and the sas appservers (note the difference in appservers) with a connected dependent desktop (java virtual machine bases) is all nice. But you must know all requirements and relationships. It is not the kiddy approach of type setup enter.

---->-- ja karman --<-----
Contributor
Posts: 65

Re: Error occured deploying the standard plan: Enterprise Miner, three Machines, JBoss

Thanks! After two days, finally I get it. One Metadata Server can only have one Middle tier. My idea is not gonna work! Thanks a lot!

Trusted Advisor
Posts: 1,300

Re: Error occured deploying the standard plan: Enterprise Miner, three Machines, JBoss

You are looking to run a clustered mid-tier, not a simple task to deploy, and certainly not accomplished through a standard deployment plan or even the deployment manager.  Hope you are familiar to JBOSS.

Contributor
Posts: 65

Re: Error occured deploying the standard plan: Enterprise Miner, three Machines, JBoss

Yes, you are right! This is the situation:

Machine A is deployed EM, I want use EM through the Web with URL "http://machine-name:8080/SASEnterpriseMinerJWS/Stauts". But not all of the computers can access  machine A's IP directly. So I want to use machine B to be a agent.

So is there a way can do it?

Valued Guide
Posts: 3,208

Re: Error occured deploying the standard plan: Enterprise Miner, three Machines, JBoss

This is the browser approach of using eminer. It will do a download of java classes and than start them with Jvm active within the browser.

You should notice the dependency of him within the browser and all the impact on versioning releases of java in the browser. The other approach is running the EM java desktop as desktop approach using a private jvm.

The midtier with the EM java add-ons is connecting to the metadata server and will use a workspace server.

The workspace server is the one needing a EM server license as running the sas processes. Machine A.

Assumed is that enterprise miners can use access this machine also by ssh or sftp. The miner project is in fact a lot of os files most of them being sas tables some of them sas catalogs and others just os types like text ones.

How would you use eminer without the needed access of this type?

---->-- ja karman --<-----
☑ This topic is SOLVED.

Need further help from the community? Please ask a new question.

Discussion stats
  • 5 replies
  • 1076 views
  • 3 likes
  • 3 in conversation