SOX v4.0 Installation Process
- Klaus-Dieter Schulz (Unlicensed)
Please be aware that there is no direct migration path for legacy SOX projects that you wish to use under SOX 4.0. To work with projects created with SOX 3.3, you will need to export them first and then re-import them into the new SOX environment. To learn more about this subject, please refer to
Workspace and Repositories and SOX Projects (SOX 3.3 or before), especially Exporting a Project and
SOX 4.0 offers a wealth of new functional features, as well as integration with a number of major third-party products. For further particulars, please refer to https://enco-software.atlassian.net/wiki/spaces/SUD/pages/2902065153#Interfaces and Integrations.
SOX v4.0 Local Installation Process (Windows Platform)
If you expect to work with locally stored repositories only, simply download the client application installer from https://www.enco-software.com/de/support/downloads/.
Our downloads are available to registered customers only. Unless you have already done, please be sure to register to gain access to our service desk facility at https://www.enco-software.com/de/registration/.
Further, use of the software requires a valid license. To learn more about SOX licensing, please refer to https://enco-software.atlassian.net/wiki/pages/createpage.action?spaceKey=SUD&title=Activating%20Your%20SOX%20License&linkCreation=true&fromPageId=3000532993 and/or SOX License Management.
The recommended installation process then involves the following steps:
The SOX download package may be in the form of a .zip archive. In this scenario, unzip (extract) all files first.
Understand that extraction may take several minutes. - Outcome: Windows will display the extracted directory within your SOX folder.
Run the sox.exe file, ensuring that you have sufficient user privileges to install the software. Depending on your system configuration, Windows may issue a warning at this point. If this happens, confirm that you wish to proceed with the installation.
Outcome: you will be asked to select your workspace, i.e., a folder in which to store your projects. SOX automatically creates a folder simply entitled “workspace” and will offer to use this folder in the first instance. It is possible alternatively to click on Browse… and nominate any other folder of your choice. SOX further offers to make your selection the default and not ask again at startup which folder you wish to use. To elect this option, check the box provided. You may alter your choice at any point from within the SOX workbench environment. When done, click the Launch button.
Next, SOX will prompt you for the repository to use with your workspace. For our example scenario, the assumption is that you wish to create a new local repository. (Also see: Workspace and Repositories.) Use the associated radio button and click on Next.
Outcome: SOX will ask you to define the path to your repository directory. Accept the default or click on Browse… to store your repository somewhere else. Enter a name for your repository. This needs to be unique within your repository directory. Click Finish to apply your choices.
Supply your user credentials to sign into SOX. As the dialog indicates, the factory defaults are “Administrator/0000” (user/password). The defaults may be subject to change by your system administrator. Check the box provided to have SOX remember your password, then click OK.
Outcome: this activity completes the setup process. SOX will display the Welcome screen.
Using a Central Repository
For the most part, the method is analogous to the one discussed before. For the sake of the documentation, we assume that the user makes a different choice for step 5 and selects a central rather a local repository.
After clicking on Next, SOX will prompt you for details relating to the remote repository:
You will need to supply at minimum the IP address and the port number for your connection. This information will be available from your system administrator. It is further possible that you will need to sign into a dedicated network or VPN. Again, query the credentials with your admin as the case may require. As illustrated above, on receiving the information required the SOX client should identify at least one remote repository. All further setup steps are identical to the local process discussed before.
Installation and configuration of client-server environment needed to use a central repository form the subject of a separate discussion; kindly refer to https://enco-software.atlassian.net/wiki/pages/createpage.action?spaceKey=SUD&title=SOX%20Installation%20Process%20%28As%20of%20SOX%20V4%2C%20an%20Empty%20MySQL%208%20RDBMS%20is%20needed%2C%20default%20character%20encodings%20needs%20utf8%20%28which%20is%20same%20as%20utf8mb3%29&linkCreation=true&fromPageId=3000532993.
SOX v4.0 System Requirements
Hardware requirements are listed at SOX System Requirements. Noteworthy are the following points:
SOX 4 requires a MySQL database, version 8.x; other databases are no longer supported.
As noted above, there is no direct migration path for legacy projects created with earlier SOX versions. To use such projects, export them from the older software, then import them into SOX 4.
https://enco-software.atlassian.net/wiki/spaces/SUD/pages/3440587467