00000 INFO 2020-01-13 17:20:30,807 mashupmgr.Deploy.DeployJob -- Failed to deploy at 13/01/20 17:20 [QuartzScheduler_Worker-1] 00000 ERROR 2020-01-13 17:21:05,308 mashupmgr.EnvironmentControllerUtils -- Failed to retrieve the runtime server for Default Application Engine in environment PROD [http-nio-8085-exec-17] Additional deploys fail with this message in the deployment log:
If successful, this browser should give an "Hello world!" message. Assuming this is successful, place a copy of the file at the root of gsoap (by default C:\Program Files\Serena\SBM\ Application Engine \webservices\bin). Then, use your browser to open the URL:
Log into the Application Repository. Under Environments, select the environment that is given in the error messages. On the Details tab, you will notice that the Runtime Server value is blank.
Application Repository log snippet ( By default this log can be found here on the Application Repository server C:\Program Files\Serena\SBM\Common\jboss405\server\default\work\jboss.web\localhost\mashupmgr\log\mashupmgr.log ) 00000 ERROR 2011-07-11 11:08:38,710 mashupmgr.ApplicationEngineDeployer -- Failed to import to Application Engine server Default Application Engine [QuartzScheduler_Worker-2]
If re-opening the most recent published version of your process app failed to correct the issue, the next step would be to rollback to the version of the process app currently deployed to runtime (i.e. your environment's Application Engine ) since we know this copy works since it was successfully deployed and currently working in runtime . This involves performing a "Get Process App from SBM Application Engine" in the Application Repository from whatever environment has the most recent deployed version of that process app and then opening that version in Composer.
Tip: Login failures are recorded in the Application Log of the Event Viewer located on the SBM Application Engine Web Server . • Authentication Sources [page 90] • Session Management [page 91]
• External Identity Provider – Select this option to have an external identity provider validate user credentials and control access to SBM. Tip: Login failures are recorded in the Application Log of the Event Viewer located on the SBM Application Engine Web Server . Session Management
00000 INFO 2017-08-02 22:23:08,326 mashupmgr.AECallbackManager -- INFO -- Export callback from Application Engine for export UUID 7e655d7c-8702-4d01-b0a2-ff47d2f914ea [http-nio-8443-exec-5]
Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out. Please verify that the server is accessible.
