![]() ![]() Patch 13951415: PATCH SET UPDATE: ORACLE ESSBASE STUDIO SERVER 11.1.2.3.001 Patch 13951408: PATCH SET UPDATE: HYPERION ESSBASE ADMIN SERVICES CONSOLE MSI 11.1.2.3.001 Patch 13951402: PATCH SET UPDATE: HYPERION ESSBASE ADMINISTRATION SERVICES SERVER 11.1.2.3.001 Patch 17323312: PATCH SET UPDATE: HYPERION ESSBASE CLIENT MSI 11.1.2.3.001 Patch 13951433: PATCH SET UPDATE: HYPERION ESSBASE SERVER 11.1.2.3.001 If you are interested here are all the patches: \common\JDBC\Oracle\11.1.2.0\lib\ wlsqlserver.jar The java classes the utility is looking for are the SQL server JDBC ones which can be found in: So basically the epmsys_registry utility can’t find required java classes when it is being run. : weblogic/jdbcx/sqlserver/SQLServerDataSourceĪt .(SQLServerSharedServicesDatasource.java:83)Īt .(SharedServicesDataSourceFactory.java:101)Īt .(SharedServicesDatabaseConnectionBuilder.java:77)Īt .(SharedServicesDatabaseConnectionBuilder.java:28)Īt .RegistryUtils.createNewConnection(RegistryUtils.java:399)Īt .Registry.lookupComponents(Registry.java:1058)Īt .ui.Console.getComponents(Console.java:269)Īt .ui.Console.generateReport(Console.java:251)Īt .ui.Console.main(Console.java:148) An exception when looking up components of type SYSTEM_TASKS_CONFIGURATION. The utility produces registry.log which is located in: The first step of the integration process is to allow OBIEE to accept the EPM SSO token when integrating with Workspace which basically means that both the EPM registry and the OBIEE version of the registry need to keep a shared encryption key, this is achieved by configuring and running the register sync utility I am not going to go through the Workspace to OBIEE integration process again as it exactly the same as I covered here. ![]() ![]() The problem was that I didn’t have access to any OBIEE environments which were configured using SQL Server so that was the first task to complete, if only my blog postings took the time it does to write them up. Now I could have left it but it would just niggle in the back of my mind until I knew if the process does have problem with SQL Server and if it is possible to succeed with the integration. ![]() I wasn’t expecting to write another update to the Workspace/OBIEE integration process but I recently saw a comment on my blog which highlighted issues when configuring with SQL Server, I must admit that I did neglect to test the configuration against SQL Server and I usually base my testing on Oracle. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |