Saturday, December 20, 2014

How To remove Box Shadow in OBIEE Dashboard


I have received below requirement from customer. He was excepting to remove the box shadow in dashboard level not for global. How to achieve this ?

 

Using the below code we can remove the box shadow in dashboard page level.

<style>

 .DashboardPageContentDiv {

   background-color:white;

   padding:0px

   }

 .SectionTable {

  background-image:none;

  border-left:none;

  border-right:none;

  border-bottom:none;

  border-top:none;

  margin-right:0px;

  margin-left:0px;

  -webkit-box-shadow:none;

  box-shadow:none

  }

</style>

 

Step 1 :

 Edit à Dashoard à Drag text object à and apply the above custom code and check the HTML check mark and save it then run it . Hurry box shadow is gone.
 
Here Is Screen shots for your reference:



 

 
 

 
Hope this Help's

Thanks,
Satya Ranki Reddy
 

 

 

 

 

Saturday, February 1, 2014

11g Error getPrincipal When Trying To Delete a Custom Role Or Group In Enterprise Manager

11g Error getPrincipal When Trying To Delete a Custom Role Or Group In Enterprise Manager

You log into enterprise Manager 11g as the web logic Administrative user. When you try to delete a custom LDAP Role
or a custom LDAP Group, which is associated with a custom role, you get the following error

The custom Role or Group did not have an associated GUID attribute for the custom Role or Group entries. The GUID
attribute should be present in both users and groups. From the stack trace, the Delete action is failing when fetching
the GUID attribute for a role or group.

For more information, see Bug 13800776 - bug 13147048

For solving this issue please follow the below steps, I have tested OBIEE (11.1.1.7.1) version. Might this solution will work OBIEE 11.1.1.5 and 11.1.1.6.

1. Backup the {Middleware_Home}/user_projects/domains/bifoundation_domain/config/fmwconfig/system-jazndata.
xml file.

2. Edit the system-jazn-data.xml file and remove the custom group entries and custom role entries in the file.

3. Save the file.

4. Restart WLS & BIEE services and test.

Thanks,
Satya Ranki Reddy

Tuesday, October 22, 2013

How to setup session timeout in OBIEE

How to setup session timeout in OBIEE 


Open instanceconfig.xml file and add the below tags and bounce the services.


<ConnectionExpireMinutes>60</ConnectionExpireMinutes>

<ClientSessionExpireMinutes>60</ClientSessionExpireMinutes>

<LogOnExpireMinutes>60</LogOnExpireMinutes>


Please look into below screen shot for you reference.

Thanks,
Satya Ranki Reddy






Monday, October 21, 2013

OBIEE11g Connection Failed Error (Import Tables)



OBIEE11g  Connection Failed Error (Import Tables)




I have several posts in OTN for not able to import tables in RPD.If you get “The connection has failed” error while trying to import data from the database using OCI call interface in RPD, perform the below steps.

  •         Try to check database whether are you able to connect database or not?

  •   Add the tnsnames.ora file in the BI Home Directory

       Ensure, you add all the data source tns entry details in the tnsnames.ora file
      Copy the tnsnames.ora file from Oracle Home (Root directory:   \App\User\Product\Network\Admin) and paste the file to the below location in OBIEE11g directory
Root directory: \Oracle\Middleware\Oracle_BI1\network\admin 
Root directory: \Oracle\Middleware\oracle_common\admin


  

  •       Add the tnsnames file location path in User.cmd file
         Add the tnsnames file location path from one of the above location in the user.cmd file. The user.cmd file is found in the below location
Root directory: \Oracle\Middleware\instances\instance1\bifoundation\OracleBIApplication\coreapplication\setup






Now, it should work. Still if you are unable to get the data, close your RPD and try it.
Restart the services.
Thanks,
Satya Ranki Reddy

Saturday, October 19, 2013

OBIEE 10g LDAP Configuration



OBIEE Security – LDAP Authentication
   
Setting up LDAP or Windows ADSI in OBIEE

Microsoft ADSI (Active Directory Service Interface) is Microsoft version of LDAP server. Most of the steps to setup of either Microsoft ADSI or LDAP server are similar. In either case, you would need help from your network security group/admin to configure LDAP. They should provide you with the following information regarding the LDAP server

·        LDAP server host name
·        LDAP Server port number
·        Base DN
·        Bind DN
·        Bind Password
·        LDAP version
·         Domain identifier, if any
·         User name attribute type (in most cases this is default)
   
Configuration steps for LDAP server in OBIEE

In Oracle BI repository, go to manage security.
  


Create a new LDAP server in OBIEE Security Manager


 
With the help from your network security group/administration, fill out the following information




Next in the Advanced tab, based on the kind of LDAP server you have and its configuration, make the necessary changes.

For Microsoft ADSI (Active Directory Service Interface), choose ADSI and for all others leave it unchecked.

Most of the times, Username attribute would be automatically generated. For Microsoft ADSI It is sAMAccountName; for most of the LDAP servers it is uid or cn. Check with your network security group/administrator on what is the username attribute for your LDAP server. Make a note of the user name attribute you will need it later.





Now we need to create an Authentication initialization block. In administration tool, under Manage go to Variables.




Under Action, go to New -> Session -> Initialization Block




Configure the session initialization block. Give it a name and click on Edit Data Source. In the pop up window, choose LDAP from the drop down box and then click on Browse. You can also configure a LDAP server here by clicking on “New”. In the browse pop up window choose the LDAP server you would like to use.





Next we need to create variables. User and Email are the common variables normally in play





Upon clicking on OK, a warning pops up on the usage of User session variable (User session variable has a special purpose. Are you sure you want to use this name). Click yes.





Next enter the LDAP variable for username. sAMAccountName in the case of ADSI as configured in the LDAP.



Hope this help’s

Thanks,
Satya Ranki Reddy