Upgrading from JBoss to Wildfly

If you are using Orchestra 6.x with JBoss, you need to follow the upgrade process below to upgrade to Wildfly, since JBoss is no longer supported in Orchestra 7.0.

The instructions below are for a system with Orchestra and Business Intelligence/Stat on separate servers and with SSL enabled. For other setups, please contact the Global Support organization.

Orchestra Server

1. Prepare an Orchestra 6.2 system with Oracle/JBoss, Business Intelligence on a separate server and same domain policy.

Make sure that the Orchestra 6.2 system is update 15 (build 3.2.0.460), or later.

2. Enable HTTPS on the Orchestra 6.2 system. For more information, see the Orchestra 6.2 Reference Manual.

3. Backup the Orchestra central installation folder, by simply renaming it.

4. Install Orchestra 6.2 with Wildfly and PostgreSQL with the same applications as in the JBoss version.

PostgreSQL is only used temporarily, it will be removed later.

5. Copy the conf/security folder from your backed up JBoss system to your new Wildfly installation.

6. Start up the new Orchestra installation and open the System Administration application. In the Parameters tab, enable SSL in the same way as in your previous system. For more information, see the Orchestra 6.2 Reference Manual.

The parameters should be set in the following way:

• HTTPS server settings: HTTPS enabled parameter enabled.

• Central WebSocket Server Settings: WebSocket enabled parameter enabled.

This is done to get HTTPS configured correctly in the file standalone-full.xml for Wildfly.

7. Enable/configure JMS bridges for supporting standalone Stat. Follow the instructions in the Setting up Stat Standalone section of the Orchestra 6.2 Reference Manual.

8. Stop the Orchestra server.

9. Copy the media folder from the backed up JBoss system to the new Wildfly installation.

10. Copy any customized widgets from the backed up JBoss system to the new Wildfly installation.

11. Copy the <Orchestra installation directory>\system\conf\ folder from the backed up JBoss system to the new Wildfly installation.

12. Reconfigure data sources to point to the old database.

The following files affect database access in some way and should be adapted:

• <orchestra install dir>\system\pentaho-solutions\system\hibernate\hibernate-settings.xml

• <orchestra install dir>\system\pentaho-solutions\system\hibernate\oracle10g.hibernate.cfg.xml

• <orchestra install dir>\system\pentaho-solutions\system\jackrabbit\repository.xml

• <orchestra install dir>\system\pentaho-solutions\system\quartz\quartz.properties

• <orchestra install dir>\system\pentaho-solutions\system\dialects\oracle10g\applicationContext-spring-security-hibernate.properties

• <orchestra install dir>\system\pentaho-solutions-jboss-oracle\system\jackrabbit\repository\workspaces\default\workspace.xml

• <orchestra install dir>\system\pentaho-solutions-jboss-oracle\system\jackrabbit\repository\workspaces\security\workspace.xml

• <orchestra install dir>\system\pentaho-solutions\qmaticbi\platform\live.mondrian.xml

• <orchestra install dir>\system\pentaho-solutions\qmaticbi\platform\qmatic.mondrian.xml

• <orchestra install dir>\system\pentaho-solutions\system\audit_sql.xml

13. Uninstall the PostgreSQL service and the QP service (which has a dependency to PostgreSQL).

14. Edit the file install-service.bat for the QP service and remove the following directive:

15. Re-install the QP service.

16. Start the Orchestra server.

Stat Server

1. Backup the installation folder by simply renaming it.

2. Install Orchestra 6.2 with Wildfly and PostgreSQL with the same applications as in the JBoss version (Stat and Business Intelligence).

PostgreSQL is only used temporarily, it will be removed later.

3. Copy the \conf\security folder from the backed up JBoss system to the new Wildfly installation.

4. Copy the \conf\stat-jobs folder from the backed up JBoss system to the new Wildfly installation.

5. Copy the following files from the backed up JBoss system to the new Wildfly installation:

• \system\pentaho-solutions\system\hibernate\hibernate-settings.xml

• \system\pentaho-solutions\system\jackrabbit\repository.xml

• \system\pentaho-solutions\system\quartz\quartz.properties

• \system\pentaho-solutions\system\dialects\oracle10g\applicationContext-spring-security-hibernate.properties

• \system\pentaho-solutions\qmaticbi\platform\live.mondrian.xml

• \system\pentaho-solutions\qmaticbi\platform\qmatic.mondrian.xml

6. Edit the <datasources> section in standalone-full.xml, by copying it from your previous JBoss installation.

7. Stop the Stat server.

8. Uninstall the PostgreSQL service and the QP service (which has a dependency to PostgreSQL).

9. Edit the file install-service.bat for the QP service and remove the following directive:

10. Re-install the QP service.

11. Start the Stat server.

12. Enable/configure JMS bridges for supporting standalone Stat. Follow the instructions in the Setting up Stat Standalone section of the Orchestra 6.2 Reference Manual. Add a jms User.

13. Set up HTTPS manually, by updating the \app\wildfly-11.0.0.Final\standalone\configuration\standalone-full.xml file:

a) Add an “orchestraSSL” security realm to the <management><security-realms> section.

b) Add the https listener to the <server name=”default-server”> section.Make sure that socket-binding uses8443.

Business Intelligence Server

1. Add the following Java option to the file \app\<wildfly-11.0.0.Final>\bin\standalone.conf.bat:

set "JAVA_OPTS=%JAVA_OPTS% -Dhttps.protocols=TLSv1.2"

All Servers

1. Upgrade Orchestra and Stat to Orchestra 7. See “Orchestra Central” .

2. Upgrade Business Intelligence to Orchestra 7. See “Business Intelligence” .