Orchestra Business Intelligence on a Separate Server
If you, in Orchestra R5.4, installed Business Intelligence on a Separate Server, see
“Deploying Business Intelligence on a Separate Server” , and now want to upgrade to Orchestra 6.0, there are a few steps you need to repeat
after Orchestra has been upgraded. This is due to the fact that certain files are overwritten, during the upgrade process.
The needed steps are described below:
1. In the file [install dir]/pentaho-solutions/system/security.properties, change central.orchestra.url to the url where Orchestra central is running. This requires restart of the Business Intelligence server to take effect.
2. Change how the Business Intelligence server auth system looks up authorizations for authenticated users. Open the following file in a text editor:
[install dir]/pentaho-solutions/system/applicationContext-pentaho-security-shiro.xml
Find the <bean id="shiroClient"> element and uncomment the bold "name" property by removing the enclosing <!- and -> brackets.
<bean id="shiroClient" class="com.qmatic.pentaho.extensions.security.QPShiroClientBean">
<property name="evictTimeMillis" value="7000"/>
<!- <property name="url" value="${security.central.orchestra.url}" /> ->
<property name="securityServiceJndi" value="java:global/qSystem/qp-central-core-ejb/SecurityServiceBean"/>
</bean>
This change enables authorization lookup to a separate server, in this case the value of the security.central.orchestra.url property defined above in the security.properties file.