Frequently Asked Questions

CodeMeter License Central

• Klap alles uit Klap alles in
• Cloud Lite URL copied to clipboard
  In this category you can find information about Cloud Lite.
  You can find the specific entries on the right side of the screen.
• Update License Central to a version 4.10 or higher URL copied to clipboard
  With the introduction of CodeMeter License Central 4.10, we have changed the framework of the web services in CodeMeter License Central from axis2 to CXF. To ensure that the connection to CodeMeter License Central can still be used, we provide a compatible endpoint: http://<HOST>:8080/axis2/services/WS<Service>. This means that in most cases it is possible to update to 4.10 or one of the subsequent versions in a compatible manner.
  
  At the same time, we have created new endpoints in the CXF framework: http://HOST:8080/licensecentral/services/WS<Service>. These endpoints are recommended for using the web services via client of CodeMeter License Central 4.10 and the following by Wibu-Systems.
  
  If you want to update your CodeMeter License Central to a version 4.10 or later, we recommend the endpoint CXF: http://HOST:8080/licensecentral/services/WS<Service>. You can find out what you need to consider or change in your application in the recommendations:
  
  Recommendations
  •Updating the clients: All clients should be switched to the new URL http://HOST:8080/licensecentral/services/WS<service>. This is the recommended default endpoint.
  •SOAP 1.1 protocol: We only use the SOAP 1.1 protocol. There is no support for HTTP bindings without SOAP. Existing bindings must be converted to the SOAP 1.1 protocol.
  •No different binding ports: There is only one endpoint. Communication only takes place via the URL in the style of http://HOST:8080/licensecentral/services/WS<Service>
  
  Hints
  
  •Problems when using the old URL: Clients that still address the web service with the old URL (“.../axis2/..”) will continue to work in most cases. However, if the address of the endpoint was determined via the WSDL provided by the web service, then the clients receive the new URL back in the WSDL, which leads to problems.
  •SOAPAction header: Web service methods that do not require a SOAP header (in particular WSSession.login) must set the HTTP header parameter “SOAPAction” to refer to the desired method (“urn:login”). Otherwise the web service call will fail with a null pointer exception (to be seen in the License Central Log: “java.lang.NullPointerException: Cannot invoke ‘org.apache.cxf.service.model.BindingOperationInfo.getOperationInfo()’ because ‘op’ is null”). If you have previously used the HTTP binding, you must therefore set the HTTP header parameter “SOAPAction” and use the SOAP 1.1 protocol (“SOAP binding”). When using the SOAP 1.1 protocol, the “SOAPAction” parameter is usually set automatically.
  •WSDL URLs: The WSDL file of a service can only be retrieved via this request -> (WSDL retrieval): http://HOST:8080/licensecentral/services/WSService?wsdl. Direct downloads of the WSDL file (e.g. as previously possible with http://HOST:8080/axis2/services/WSService.wsdl) are no longer valid!
  
  
  We also strongly recommend the use of a test system in which not only the functional but also the technical connection tests are carried out. If you are a Wibu-Systems hosting customer, we will be happy to provide you with such a system!
  
  When using the SAP Connector from Informatics or the License Central Extensions from Wibu-Systems, there should typically be no problems with the changeover. If you do, please contact Wibu-Systems Support with a description of the problem. We will be happy to help you.