SAFE X3 V2 configuration console > Specific actions with the SAFE X3 V2 configuration console 

Data servers

 
Moving the tablespaces

If you want to move the tablespaces in your database after its configuration by the console, it is imperative that you modify your adcrap file and the database.adonix.oradirdat tag in the adxinstalls.xml files of the database server and in the solution.xml file in your application server.

Configuring a disconnected database

This functionality is used to integrate a database server not accessible by the console to a Sage solution. The two main reasons why the console cannot access a database server are :

  • The operating system of the database server is not supported by the Sage product scripts.
  • it is for important security reasons that the console should not have access to this database server.

Therefore in this specific case no ADXADMIN administration engine is required on the data server.

The "Data" button is then used to launch the generation of the database creation scripts locally, but they are neither transferred no executed on the database server. Because the console does not have access to the database server, it is up to the user to manually transfer and execute the generated scripts.
The user must create the directory structure on the target server in the way that is entered in the database component setup. It is then necessary to launch the database creation scripts that the user has made available in the script directory.
In Windows with a SQLServer database, launch the script "database_CrDb.bat".
In Windows with an oracle database, launch the different scripts "cr(nombre)_base_ORASID.cmd" in the specified order.
In Unix, launch the different shells "launch_ORASID_(nombre).sh" in the specified order.

Don't forget!

Remote/disconnected Oracle databases and remote connections.

If a disconnected database is created from the user's own scripts or the user modifies the scripts generated by the console, the following prerequisites need to be complied with:

  • the database SID must be a capitalized character string,
  • the database mut be in UTF8 or AL32UTF8,
  • the open_cursors setup must be at least equal to 300.

Upon configuration of the database in order to integrate the main folder, the console is requested to launch the creation script of the application roles, that is, the roles.sql script created in the tmp directory of the main connection server. For that purpose, the console uses the DBMS server configured with the main connection server and the SYS account previously configured in the database component. It is therefore important to update the SYS user password in the Database component.

In the event of an error of type "SYS user cannot connect to database: SP2-0640: Not connected", there are two most frequent origins.

  • In the event of remote or disconnected databases, it is important to be able to rely on a configured and working Oracle listener.
  • For the Oracle databases on Unix platform mainly, you may have to authorize the remote connections of the SYS user by means of the "orapwd" Oracle utility.

In the latter case, ask your Oracle database administrator to create a password file for your Oracle instance with the "orapwd" utility. Usually this file is created by the 'launch_ORASID_3.sh' script generated by the Sage X3 configuration console. Make sure that the owner of this file is also the owner of the installation of the database software, in most cases it is the 'oracle' user. Make sure that this prerequisite is complied with before the 'Application' component of your solution is configured in the SAFE X3 V2 configuration console.

During the main Process server component configuration, it is necessary to enter the path for the DBMS client in the advanced parameters, "remote database" section. Make sure that the version of your DBMS corresponds at least to the version of your DBMS server.

Process servers

Update of the serialization file

To update the serialization file with the SAFE X3 V2 Configuration console, open the solution in the console, select the main process server from the list of process servers (Process server tab). In the list of the main process server parameters, specify the new serialization file path and click on the configure button.

Changing the service port number

To change the service port number of the process servers for the solution, open the solution in the console, in the first tab, change the service port number and click on the configure button. After this action, all the additional process servers have the status UPDATE. You must reconfigure them in order that they take into account the new port number.

Printing the ADXVOLUMES

The console is used to print the AdxVolumes file for your solution. Open the solution in the console, in the Process server tab, select the principal process server, click on the ADXVOLUMES button, a dialog box will then appear containing the contents of the AdxVolumes. Carry out the necessary modifications and click on the OK button so that the modifications will be transferred to the application server.

Solution components

Forcing the deconfiguration of a Safe X3 Web server

The deconfiguration of a Web Safe X3 Web Server is prohibited whilst solutions are published on this server. The published solutions can be locked if your console cannot access them. In certain cases it is necessary to be able to bypass this prohibition and force the deconfiguration of the component. To force this deconfiguration, add the config.web.configuration.resetenabled=true value in the web tab of the console preferences. Click on the Deconfiguration button, a message appears stating that this action is not recommended but you can force it. Click on OK to start the deconfiguration.

Forcing the deconfiguration of the print server Safe X3 Print Server

The deconfiguration of the print server is prohibited whilst solutions are published on this server. The published solutions can be locked if your console cannot access them. In certain cases it is necessary to bypass this prohibition and force the deconfiguration of the print server. To force this deconfiguration, add the config.report.configuration.resetenabled=true value in the web tab of the console preferences. Click on the Deconfiguration button, a message appears stating that this action is not recommended but you can force it. Click on OK to start the deconfiguration.

Forcing the deconfiguration of a documentation server

The deconfiguration of a documentation server is prohibited whilst solutions are published on this server. The published solutions can be locked if your console cannot access them. In certain cases it is necessary to bypass this prohibition and force the deconfiguration of documentation server. To force this deconfiguration, add the config.documentation.configuration.resetenabled=true value in the documentation tab of the console preferences. Click on the Deconfiguration button, a message appears stating that this action is not recommended but you can force it. Click on OK to start the deconfiguration.

Force the deconfiguration of a Safe X3 Java Bridge Server.

The deconfiguration of a Safe X3 Java Bridge Server is prohibited whilst solutions are published on this server. The published solutions can be locked if your console cannot access them. In certain cases it is necessary to be able to bypass this prohibition and force the deconfiguration of the component. To force this deconfiguration, add the config.javaserver.configuration.resetenabled=true value in the javaserver tab of the console preferences. Click on the Deconfiguration button, a message appears stating that this action is not recommended but you can force it. Click on OK to start the deconfiguration.

Force the deconfiguration of a Safe X3 Business Intelligence Server.

The deconfiguration of a Safe X3 Business Intelligence Server is prohibited whilst solutions are published on this server. The published solutions can be locked if your console cannot access them. In certain cases it is necessary to be able to bypass this prohibition and force the deconfiguration of the component. To force this deconfiguration, add the config.business_objects.configuration.resetenabled=true value in the business_objects tab of the console preferences. Click on the Deconfiguration button, a message appears stating that this action is not recommended but you can force it. Click on OK to start the deconfiguration.