Deconfiguration method for a Sage X3 solution
The following method gives the logical order used to deconfigure a complete solution (with linked servers).
Step 1: Depublish and deconfigure the Safe X3 Web Server
- Depublish the web services connection pools connected to the solution
- Depublish the solution published on the Safe X3 Web Server
- Deconfigure the component
Note: In order to deconfigure a Safe X3 Web Server component, you must have previously depublished all the solutions that it publishes. In order to deconfigure a solution, you must have previously depublished it on all the linked servers that publish it.
Step 2: Depublish and deconfigure the Safe X3 Print Server
- Depublish the solution published on the print server
- Deconfigure the print server
Note: To deconfigure a print server, you must have previously depublished all the solutions that it publishes. In order to deconfigure a solution, you must have previously depublished it on all the linked servers that publish it.
Step 3: Depublish and deconfigure the documentation server
- Depublish the published solution on the documentation server
- Deconfigure the documentation server
Note: In order to deconfigure a documentation server, you must have previously depublished all the solutions that it publishes. To deconfigure a solution, you must have previously depublished it on all the documentation servers that publish it.
Step 4: Depublish and deconfigure the Safe X3 Business Intelligence
- Depublish the solution published on the SAFE X3 Java Server
- Deconfigure the Safe X3 Business Intelligence component
Note: In order to deconfigure a Safe X3 Business Intelligence component, you must have previously depublished all the solutions that it publishes. In order to deconfigure a solution, you must have previously depublished it on all the linked servers that publish it.
Step 5: Deconfigure the additional X3 process servers
- Deconfigure all the additional X3 process servers for the solution
Note: The main X3 process server deconfigures itself with the application server.
Step 6: Depublish and deconfigure the Safe X3 Java Bridge Server
- Depublish the solution published on the Safe X3 Java Bridge Server
- Deconfigure the component
Note: In order to deconfigure a Safe X3 Java Bridge Server, you must have previously depublished all the solutions that it publishes. To deconfigure a solution, you must have previously depublished it on all the linked servers that publish it.