Migrating eDeveloper V10 Web Services into Magic xpa (Magic xpa 3.x)
Q. The service is created and deployed using eDeveloper V10. Is it necessary to re-deploy the service in Magic xpa using the Web Service Interface Builder?
A. On the provider side, the service is already deployed, so there is no need to re-deploy it.
Q. When Magic xpa is the Consumer side, is it necessary to re-deploy through setting/services?
A. As the consumer, the client files are created after loading the service. Instead of reloading the service, the following changes can be done in order to consume the service from Magic xpa:
-
To consume the service, the jar and xsd files are required. These files are created in the SoapClientModules directory. These files can be copied to the directory of the service from SoapclientModules of version 10 to Magic xpa. For example: Test1 is a Web service that was called from eDeveloper V10. Therefore, in the SoapClientModules directory there is a directory called Test1 that contains the client files for consuming this service. Copy the Test1 directory under the Magic xpa SopaclientModules directory to consume it from Magic xpa.
-
From the V10 magic.ini file, copy the line of Test1 service from the Services section to Magic xpa's magic.ini Services section.
Q. When the provider machine is changed to another machine, do we need to copy the Systinet\app folder's JAR and deploy it manually, or can we copy the Magic\Builders\WS folder's JAR?
A. Copy the jar file to the new provider machine and deploy it manually. These files can be copied from Systinet\app or Magic\Builders\WS. Both the files are same.
