Also, you have happened that you needed to have multiple running instances of Oracle BI and you did not have enough physical servers?You needed to have when developing applications in Oracle BI also have two different versions of the repository and the presentation catalog? It would be useful to take advantage of separate development and test server without having to install on another environment? Of course, the result can be achieved by splitting machines and virtualization of hardware resources available to us, two virtual servers. With a bit of skill but can get by with a single server operating system with a single installation of Oracle BI, which we can get a solution with two separate repository, presentation catalogs and URLs for user access. The principle of parallel run "two in one" achieved with a few basic properties Oracle Business Intelligence:
Preparation of the second ODBC connection
while a standard ODBC connection to the BI Server called AnalyticsWeb automatically accesses the repository, which is labeled as DEFAULT, to make the second repository is necessary to create a second ODBC connection with a different name. The settings of this connection, enable the "change the default repository that" as the value and put Star2. Application Server is now necessary to create a second application "analytics" on the application server. BI Server in the directory "... \ OracleBI \ web \" is available analytics.war file, which for use on my Tomcat renamed (eg analytics2.war) and we will deploy new applications (to deploy to OC4J will use http:/ / localhost: 9704/em). After the successful deployment of the second application must modify the web.xml configuration file that is stored in the application server, WEB-INF. [tomcat: C: \ Program Files \ Tomcat 6.0 \ webapps \ analytics2 \ WEB-INF \ OC4J: C: \ oracle \ OracleBI \ oc4j_bi \ j2ee \ home \ applications \ analytics \ analytics2 \ WEB-INF \] In the web.xml file change the port number from 9710 to the 9712th The result of this step are two URLs, for example:http://localhost:8080/analytics http://localhost:8080/analytics2 Two instances of the presentation server The last step is to run two separate instances of BI Presentation Server so that each was associated with one applications and application server that was connected to various BI Server repository. To this end we make two copies of the configuration file InstanceConfig.xml that found in the directory ... \ OracleBIData \ web \ config \. New store a copy in the same directory and name instanceconfig_9710.xml andinstanceconfig_9712.xml . In the file instanceconfig_9712.xml then change:
- BI Server is able to load multiple repositories simultaneously (one BI Presentation Server, however, real-time access to only one).
- The ODBC connection BI Server and BI Presentation Server you can define which repository to be used.
- You can run multiple instances of BI Presentation Server on one machine with different parameters.
- Applications can be deployed on application server several times under the rune names.
- one of the repository is marked as default,
- Star, respectively. Star2 the internal logic repository indication that we will continue to work
Preparation of the second ODBC connection
while a standard ODBC connection to the BI Server called AnalyticsWeb automatically accesses the repository, which is labeled as DEFAULT, to make the second repository is necessary to create a second ODBC connection with a different name. The settings of this connection, enable the "change the default repository that" as the value and put Star2. Application Server is now necessary to create a second application "analytics" on the application server. BI Server in the directory "... \ OracleBI \ web \" is available analytics.war file, which for use on my Tomcat renamed (eg analytics2.war) and we will deploy new applications (to deploy to OC4J will use http:/ / localhost: 9704/em). After the successful deployment of the second application must modify the web.xml configuration file that is stored in the application server, WEB-INF. [tomcat: C: \ Program Files \ Tomcat 6.0 \ webapps \ analytics2 \ WEB-INF \ OC4J: C: \ oracle \ OracleBI \ oc4j_bi \ j2ee \ home \ applications \ analytics \ analytics2 \ WEB-INF \] In the web.xml file change the port number from 9710 to the 9712th The result of this step are two URLs, for example:http://localhost:8080/analytics http://localhost:8080/analytics2 Two instances of the presentation server The last step is to run two separate instances of BI Presentation Server so that each was associated with one applications and application server that was connected to various BI Server repository. To this end we make two copies of the configuration file InstanceConfig.xml that found in the directory ... \ OracleBIData \ web \ config \. New store a copy in the same directory and name instanceconfig_9710.xml andinstanceconfig_9712.xml . In the file instanceconfig_9712.xml then change:
- DSN - name of the ODBC connection, pointing to non-default repository
- Listener port - the new value of 9712
- CatalogPath-catalog presentation to be used
Posts
