Minimum solution

Configuration

Create the solution

In order to create the solution, open the Solutions left list and click on the Solution addition button.

A dialog box entitled "Create a new solution" is used to build the whole minimum solution using the components that have already been placed on the available servers.

The process starts with the selection of the APPLICATION component that determines the product and hence the solution type. The console will then submit a list of main process servers available for your solution.

It will then be possible to choose the database type (administered or not) that should be used with your solution. If you select an administered (connected) database, you need to select a database component available on a server. If you select a disconnected database, in other words, a database created by you and that cannot be accessed through an ADXADMIN administration engine on the server, you need to enter all the parameters necessary to create a virtual database component that will match your disconnected database. For further details on the database, refer to the Specific actions with the SAFE X3 V2 configuration console documentation.

The last phase enables you to enter an identifier, a description and a message (optional) defining your new solution. If you enter a message, it will be displayed each time the solution is loaded onto the console. This can be useful if you manage many solutions, adding a message on opening critical solutions is used to gain your attention and avoid confusion with test solutions.

Once this information is validated, the Console displays the solution configuration screen. The setup components of the servers for the solution are loaded with the components that you have selected.

Configuring the database server

In order to install the solution, it is necessary to load and configure the mandatory component "Database server" first.
The console is used to reference a database considered as "disconnected". The principle is to create a solution in which the database server cannot be accessed from the console. For more information on adding a disconnected database, click here...

The component status is "Idle", on exiting the configuration it becomes "Active".

Configuration

To configure the database server component, enter the mandatory parameters (Only the instance in the case of SQL Server must exist beforehand, the console is responsible for the database creation (Oracle or SQL Server) and the ODBC source (SQL Server):

Once these parameters are entered, click on the Save button of the Configuration console.

To start the actual configuration of the database server, click on the Data button. A dialog box appears displaying the different configuration options.

Three options are proposed:

• Script generation: Generation of the database creation scripts in the script directory of the database component on the server. This option can be used to introduce modifications to the scripts directly from the scripts display/modification screen.
• Script execution: Running of the scripts located in the script directory of the component. This option is used to subsequently run scripts that have been modified by means of the 'Script generation' option. 
• Full configuration: Linking of the two previous options into a single step (no script modification possible)

To configure the database component, select the 'Full configuration' option and validate.

On exiting the configuration, the component status becomes "Active".

In order to solve the most common problems upon configuration of the databases, consult the field "To know" by clicking here...

X3 application and main process server components

The configuration of these two components is dependent on the correct configuration of the database server component.

By a single action, the configuration of the application server and the main process server is carried out.

The value of the parameters needs to be checked first:

• SAFE X3 process server 
• SAFE X3 service port number: it specifies the port to be used by the main process server service.
• Sage Serial path (up until V6 version): it specifies the local path to recover the Sage license and copy it onto the remote server.
• for a Distant database (up until the V6 Version, these parameters are only available in advanced parameters):
• DBMS client path: ORACLE client installation path.
  It is necessary to click on this setup to enable the Console to search for possible values. If the ORAHOME variable is defined, the Console proposes that its value be recovered. Make sure that the version of your DBMS corresponds at least to the version of your DBMS server.
• Name of the link to the remote database: Access link to the database.
  This value must be left blank. On exiting the configuration this parameter will have as its value the name of the Runtime component.
• the account and possibly the password of the account to be used to run the service.
• Sage application server
• Apache installation path: it specifies the installation path of the Apache http web publication server.

Note: In the case of Oracle, the Console will create its own TNSNAME.ORA file in the "Runtime" directory of the solution. In this way, the original Oracle file will not be impacted.

Note concerning the Apache setup: For those configurations intended for a large number of users, or for the use of the HR portal module, it is possible to configure and optimize the Apache process model parameters in the advanced parameters of the application component. These parameters can be accessed in the "Application server->Web parameters->Process template". The process model category is dependent on the target architecture and the configuration of the Apache software.
To activate the Apache setup options, the "Configuration of the process template" parameter in the "Web parameters" category must be switched to the "True" value.

Warning: It is recommended to use a dedicated Apache installation when using the Apache process model parameters in order to avoid possible problems with the values of another solution using the same Apache server.

Note concerning the low-performance systems and virtualized systems:
When duplicating or transferring folders from one solution to another, if you encounter errors such as:
"ERROR - Error when exporting folder tables
NOK
The process cannot access the file as this file is used by another process.
The process cannot access the file as this file is used by another process.
The process cannot access the file as this file is used by another process."

You need to modify the value of the "Configuration script time delay" parameter to set it to "True" in order to add time delay in the configuration and export scripts created by the console. This parameter adds a second between the processing of each table on data export. This leaves enough time for the system to synchronize the file system. This rather significant addition of one second per table to the total export time is the one drawback. As a consequence the export is longer (around 17 minutes for 1000 tables).

Once all the parameters have been entered, click on the Save button.

To launch the actual configuration of the Application and main process server components, click on the Application button.

On exiting the configuration, the ADXD process of the main process server is launched and the status of the components is "Active".

At this stage, the solution can be used. It is therefore possible to connect via the Client SAFE X3 workstation to the application for the solution up to the V6 version or via a web browser and an access point from the V7 version.