Chapter 3: Sage X3 JAR File Upload

The following configuration setting is required to set up the Java bridge server of Sage X3, allowing the setup of the integrated service. Sage X3 JAR file upload is important for real-time customer update changes to work from Sage X3 to Sage CRM.

Note: Please note that, before uploading this Jar file, the Java Bridge service should be already installed/configured in your Sage X3. There are 2 ways to deploy the JAR file on the Java Bridge Server.

For Sage X3 v6.5 - Kindly use the JAR file for uploading from the below V6.5 folder (i.e. C:\Program Files (x86)\Greytrix\GUMU for Sage CRM - Sage X3\Patches\V6.5). Assuming the Greytrix setup is installed in C drive.

Please use the below URL to upload the jar file: http://localhost:27880/infos/index.jsp

For Sage X3 v7 and above - Kindly use the JAR file for uploading from the below V7 folder (i.e. C:\Program Files (x86)\Greytrix\GUMU for Sage CRM - Sage X3\Patches\V7 OR Above. Assuming the Greytrix setup is installed in C drive.

Please use the below URL to upload the JAR file http://localhost:27880/safex3/#/safex3/home.jsp

A. Cold deployment:

Placing the JAR file directly in the bundles' folder of the java bridge server is nothing but cold deployment (i.e.at D:\Sage\SafeX3\JAV220\data\extends\bundles) (assuming Java Bridge Server is installed on D drive). Though this is a shortcut to deploy the jar file in the bridge server. For this, you will need to stop the Sage X3 Java core server services and then place the jar in the Java Bridge Server. After placing the jar, you will need to restart the Sage X3 Java core services. For doing this, kindly follow the below steps

  1. Open the Run command (windows) and type “services.msc” then click ok. The services window will open.

  2. Stop the services of Sage X3 Java core server services if already started stopping the services is mandatory for cold deployment.

  3. Place the JAR file in the bundle's folder of Sage. In my system, the Sage X3 Java core server is located at D:\Sage\SafeX3\JAV220\data\extends\bundles (assuming Java Bridge Server is installed on the D drive.

  4. After the placement of JAR, start and restart the services of the Sage X3 Java core server.

** This type of deployment is not recommended in real-time.

B. Warm deployment:

Placing the jar using the User interface (UI) i.e. through a web browser. Confirm that the Sage X3 Java core server services are registered and running in the system in which you are going to deploy your jar. On the confirmation check if the JAVA bridge server is set up and operational. Use the mentioned URL link to check if the HTML UI is accessible: http://localhost:27880/infos/index.jsp.

27880 is the default path for the JAVA bridge server, but this might be different in your system if the default path was changed during installation. To confirm your Port number, please follow the below steps:

i. Open SAFE X3 Consoles. ii. Select SAFE X3 Java Servers. iii. Click on Configuration. iv. Check Runtime.bundle_deamon.adxd.port.

If it is installed correctly, you should be able to see the following screen:

  1. Now, submit the Java Extension bundle to the JAVA Bridge Server. Click on the Extension menu in Safe X3 Java Bridge Server and then proceed by clicking on Submit a bundle link present at the end of that menu.

  2. Click on the [Browse] button, and browse for uploading the jar file in the Java bridge server. The folder where you exported the jar files from eclipse.

3. Once the bundle is uploaded successfully, a screen like the following will be displayed:

4. You can cross-check by refreshing (F5) the same page. If the jar uploaded is successfully listed with the server.

5. Navigate to the services.msc as mentioned previously, where you could see if your Sage X3 Java core server is in the start or stop mode. Restart the Java Bridge Server so that the new plug-in jar is in effect after this activity.

To start the Webservices to be used by X3 below configuration is to be done

Ideally, when we run the component the web service should be enabled for Admin users. To confirm the same follow the below steps:

Ø To configure the settings Go To Administration ->System->Web Services Ø Enable web services to Yes Ø Dropdown fields as the string are WSDL file to YES Ø Make WSDL available to all YES Ø Force web service log on to Yes Ø Below is the screenshot for a better understanding

Last updated