When preparing the installation of OIM Suite Bundle Patch 6 i had to import the for supplied BI Publisher report artifacts. These supplied artifacts, reports and datamodels, are logically grouped in folders and sub-folders. For example; the "Access Policy Details" and "Access Policy List by Role" reports and reportmodels are grouped in the "Access Policy Reports". The BI Publisher catalog utility, BIPCatalogUtil.sh", has an import parameter, basedir, for importing a set of reports or data models. When importing the reports using the basedir, you probably will get, like me, a java.lang.StringIndexOutOfBoundException. Read More...

Since the release of Siebel 8.1.1.1 and BI Publisher 10.1.3.4.1 a new security model is introduced in BI Publisher, Siebel Security. When using the Siebel Security model, BI Publisher relies on Siebel for its authentication and authorization. Siebel employees can be authorized to generate reports by assigning them the necessary responsibilities. Oracle officially only supports the Siebel Security model when using DB Security for Siebel and the use of the BI Publisher LDAP security model when using LDAP Security Adapter for Siebel. In fact Oracle names the combination of Siebel LDAPSecAdpt with BI Publisher Siebel Security model a 'mixed authentication method' and has not certified and/or validated this method yet. The BI Publisher LDAP Security model has one disadvantage, it requires hardcoded LDAP Security Groups like XMLP_DEVELOPER. Groups names like these probably do not follow your company naming standards for LDAP objects and are therefore not allowed. If so this immediately makes BI Publishers LDAP Security Model not suitable for implementation in your production environment. If you have a better understanding of how the
Siebel Security model works, it is fairly simple to implement this security model when using the LDAPSecAdpt for Siebel.

Tweet
Read More...

In Siebel 8.1.1.1 and BI Publisher 10.1.3.4.1 a new security model, Siebel Security, is introduced. In this security model BI Publisher uses the Siebel responsibilities as functional roles. How to deploy this is excellent described in the Blog Siebel Essentials. When the Siebel Security Model in BI Publisher requests the available roles (responsibilities) in Siebel, the username and password of the Siebel administrator and the Siebel user are passed in clear-text in the header and body of the webservice call. It would be more secure when you could make a secure (HTTPS) webservice call to your Siebel Web Server. This article describes how you can achieve this.

Tweet
Read More...