Can I roll back to ROB-EX 6.4 after upgrading the ROB-EX Server, if needed?
No. ROB-EX 7.0 Server migrates the multiuser database to a new format. You should always backup the existing multiuser database before migrating to 7.0. You can choose to create a new database and restore the backup in the new database or migrate the existing after the backup.
Guide to how you can approach this is in the manual:
7.0 Server migration
Should I use the ROB-EX 7.0 installer to *update the existing ROB-EX Server-installation?*
No. The 7.0 Server-installation has a new design and the old design can not be upgraded cannot be updated using the 7.0 installer. You can choose to install the new ROB-EX server alongside the old one and disable the old service.
How is the database migrated to the 7.0 design?
When starting the 7.0 Server service for the first time, the database format is migrated to the new format. The first startup will consequently take a longer time because of this.
I have implemented custom tables and/or fields to the GanttMultiuser database. Will this be an issue?
As described, you should always create a backup before migrating to 7.0. If you have done custom modifications to the ROB-EX database, these could potentially cause issues as they are not provided by or tested by ROB-EX.
Run the migration in a test environment first to verify that the migration is successful.
Can I install the new 7.0 ROB-EX Server without setting up a database or migrate and existing?
Yes, just blank all the fields in the dialogue when the installer asks for database information. The service will be installed, and you can then later direct the service to a database of your choice.
Do I need to install a new ROB-EX License Server using the new installer?
No, but we recommend updating the existing one. Features have been added to the License Server that could be useful later if de-bugging is needed.
I try to update ROB-EX Planner, but I get an error related to awt.dll?
The installer is trying to update the embedded java. Make sure the tray console for the Integration Client is exited and try again.
Is Java Jre and/or JDK still required for the ROB-EX environment?
No, all the ROB-EX components have embedded java.
Make sure that registry and/or JAVA_HOME is directed to using the embedded java if you choose to remove any 3rd party Java installations that the system has been using.
I have upgraded to ROB-EX 7.0 and now the users cannot log in?
The ROB-EX 7.0 is using a new login URL and port for the Desktop client. If the users try to log in using e.g. ServerName:11099 (the old pre 7.0 style) after the upgrade, the login will fail.
The new login URL syntax and the default port is http://ServerName:6565.
How can I edit the ports used by ROB-EX Server and/or edit the database URL?
The new ROB-EX Server 7.0 uses the information written in the file “application.yml”. The file can be edited in a standard text editor.
The file can be found in the ROB-EX server installation (default directory is ROB-EX\ganttServerG2).
I upgraded to ROB-EX 7.0 Multiuser and now I cannot access the ROB-EX Web Administrator?
ROB-EX 7.0 Multiuser is using a new URL and port for login.
The default URL and port are http://ServerName:9090. Port can be edited in the file “application.yml”.
Guide for the new WebAdmin can be found here: Multiuser server
I am not able to access Dashboard. How can I log in?
Environment security has been boosted in ROB-EX 7.0. As a result of this, accessing Dashboard requires login. You can create dashboard logins via the ROB-EX WebAdmin or assign Dashboard login to existing users/AD mappings.
The Dashboard login role is “Web-Dashboard”.
We love the new Gantt chart in ROB-EX Dashboard. Is it using a client license from my license pool?
No.
We love the new Gantt chart in ROB-EX Dashboard. Can I use it instead of a ROB-EX Planner client?
No. It’s a view-only chart.
Does ROB-EX 7.0 Multiuser use the same ports as version 6.4 or older?
No, this architecture has been streamlined and now only uses:
6565 Default multiuser login port for service 1
9090 Default port for WebAdmin
What port number is used for Dashboard, Time Tracker, and Resource Monitor?
The service port used by ROB-EX Integration Client is the port number you need to set in the URL.
If no Integration Client is installed, use the REST port.
See more about REST at REST
Can I access ROB-EX Dashboard when running a standalone ROB-EX Client
Yes, but you need to set the standalone client to run the REST server. ROB-EX Dashboard data is updated via REST calls.
The login is defined by the REST user+password.
See more about REST at REST
Can I set the ROB-EX services to use AD account to run the service?
Yes, but for ROB-EX Server you must use the sqlserverAD-profile in spring profiles in application.yml and blank the username and password.
If you are updating a very early ROB-EX 7.0 version (prior to 7.0.0.93), the sqlserverAD-spring profile may not be listed. If the sqlserverAD-spring profile is missing in the application.yml, you can insert this line:
active: sqlserverAD
For the other ROB-EX services, you can change this via the specific service Log on-tab in windows services.
Can I modify the operation text shown in the Dashboard Gantt chart?
Yes, there are some options for this.
See this section of the manual: Dashboard system configuration
Do I need Admin level log in to access Dashboard?
No. You need a dashboard rule set up to your login or use a created dashboard user login.
I am upgrading to ROB-EX 7.0 and using GanttERP/GanttERP2. Should this be upgraded as well?
Yes, If you are using GanttERP or GanttERP2 this should always be upgraded to match the ROB-EX version you are running.
SQL upgrade-tools can be found in .\ROB-EX\Planner\plugins\erp:
ms-sql-db-update for GanttERP
ms-sql-db-updateVersion2 for GanttERP2
Do I need a new license key for ROB-EX 7.0?
No, ROB-EX 7.0 is using the same license tech as 6.4/6.4.1.
How can I change the socket timeout for the database connection?
We use a new driver for database communication. The default socket timeout is set to infinite and you don’t have to modify it compared to earlier ROB-EX Server-versions where the default value was 1 minute.
ROB-EX Server service is running using Local System, but the Integration Client is using Local Service. Why is that?
We use Local Service since it is best practice to assign the least possible authorization rights to services.
ROB-EX Server uses Local system since our experience shows that Local Service does not have the necessary rights when querying the AD. The ROB-EX Server service needs to query the AD, since it handles the login of users through Windows AD.
By default there is no users.xml installed during setup. You have to figure out which fields need to be activated to use the Shopfloor?
The Users.xml-file is a part of the Operator -version of the Planner. It is default located in ./config. When Shopfloor is started for the first time, it will be copied to ./custom.
Do I need to install a Planner with Operator to use Time Tracker?
Yes, the Time Tracker plugin is installed when installing a Planner with Operator. If you upgrade an existing or older version of ROB-EX and it was not installed with Operator (or Shopfloor for older versions), the plugin for Time Tracker will be missing.
Time Tracker also requires the client running REST to be logged in to a ROB-EX Multiuser environment.
Post your comment on this topic.