System Services fail to start after upgrade

Post any questions regarding Installing or Upgrading to V5, including problems starting and using the Ebase Server or Designer

Moderators: Jon, Steve, Ian, Dave

Jon
Moderator
Moderator
Posts: 1342
Joined: Wed Sep 12, 2007 12:49 pm

System Services fail to start after upgrade

#1

Postby Jon » Wed Jul 15, 2015 8:45 am

The Logon Service and Workflow Assignment Service fail to start after upgrade to V5.0 and issue an error message saying service ebaseLogonService not registed. This problem applies only when an explicit URL has been configured for the service in the V4 property files i.e. either/both of:
o property Logonexit.WebServiceUrl in Xisecurity.properties
o property Assignment.Handler in Xiassignment.properties
Last edited by Jon on Wed Jul 15, 2015 9:00 am, edited 1 time in total.
0 x

Jon
Moderator
Moderator
Posts: 1342
Joined: Wed Sep 12, 2007 12:49 pm

#2

Postby Jon » Wed Jul 15, 2015 8:58 am

This problem applies only to the first V5.0 beta - 20150706.

Follow these instructions to fix this problem after the upgrade:
  • 1. Edit file tomcat/<webapp>/ebaseConf/security.properties, remove property Logonexit.WebServiceUrl if it exists.
    2. Edit file tomcat/<webapp>/ebaseConf/workflow.properties, remove property Assignment.Handler if it exists.
    3. Edit workspace file System Services/Services/LOGON_SERVICE.eb (this is an XML file) and add inMemory="true" to the webServiceConfiguration element towards the bottom of this file. It should look like this:

    Code: Select all

    <webServiceConfiguration name="ebaseLogonService" enabled="true" soapVersion="http&#58;//schemas.xmlsoap.org/wsdl/soap/" inMemory="true"/>
    4. Repeat this exercise for workspace file System Services/Services/WORKFLOW_ASSIGNMENT_SERVICE.eb.
    5. Restart the server and the designer.
The Workspace directory is located at the root of the Ebase file system.
0 x


Who is online

Users browsing this forum: No registered users and 96 guests