Start ONLY Serena Common JBoss. Wait until you are able to open the SBM Application Repository login page (URL: http://MyServer: 8085/mashupmgr / ) Start IIS.
Log into the Application Repository ( http://server: 8085/mashupmgr ). Switch to the Privileges view. Select your user, and verify that you have all privileges, including Delete Process App, Delete App/Orch, and Break Lock.
Edit the file "Program Files\Serena\SBM\Common\jboss405\server\default\deploy\mashupmgr.war\WEB-INF\mashupmgr.cfg" on the Application Engine server to which you are trying to deploy. Uncomment out the "callback.web.context" section, and put in the Repository ( Mashup Manager ) URL ( i.e. http://server: 8085/mashupmgr ). Restart the Serena Common JBoss service.
Edit the file "Program Files\Serena\SBM\Common\jboss405\server\default\deploy\mashupmgr.war\WEB-INF\mashupmgr.cfg" on the Application Engine server to which you are trying to deploy. Uncomment out the "callback.web.context" section, and put in the Repository ( Mashup Manager ) URL ( i.e. http://server: 8085/mashupmgr ). Restart the Serena Common JBoss service.
Log into the Application Repository ( http://servername: 8085/mashupmgr ) Under Environment, click on the environment to which you are trying to deploy. Go to the Endpoints tab.
... returned for the IP address of that server ... As of JRE 1.6.0_22 this is deemed to be a security violation (cross- site scripting attack), and access is blocked unless there is a special file that indicates which cross- site scripting is allowed. ... In the URL that is used to access the VM I-Net server, only use the name that is returned for the IP address of that server. This will yield a consistent name -> IP address -> name lookup, and avoid the problem.
