I'm currently working on Row Level Security and Trying to study the File Contents of the OBIEE Dashboards once exported as .BAR File .
The issue I'm facing is that the newly created User Names are not showing up in the contents of the Extracted .BAR File .
( Folder Path : <.BAR File Root> \content\catalog\root\users )
To add in more, I created two new users namely : User_1 and User_2 .
And I implemented Row Level Security for both . After Extracting it as .BAR and unzipped it , the User_1 Folder is present in the Folder Location and User_2 Folder is not present .
Note : Role Level Security is working fine with both Users as they log in .
I have tried to down the services and again started up the services but haven't made any differences .
I request to give any suggestions to resolve this issue or any other ways to make the changes made in OBIEE reflect .
Thanks in Advance .
Users and credentials are not exported in BAR files
They must be exported/imported separately using the weblogic console
To export security data to a file:
In the left pane, select Security Realms and then select the realm whose security data you want to export (for example, myrealm).
Expand Migration > Export.
In the Export Directory on Server field, specify the directory on the Administration Server to which to export the security data.
Click Save.
The security data is saved in a file in the location you specified.
It looks like you are exporting user folders, not users
oracle docs: https://docs.oracle.com/cd/E24329_01/apirefs.1211/e24401/taskhelp/security/ExportDataFromSecurityRealms.html
The OBIEE have mentioned that they have removed the Support for Extracting the .BAR Files of the Dashboards from Version 12.2.1.4 .Now I'm able to export the .BAR Files in the Version 12.2.1.3 where they have given a Disclaimer that they will stop the support to extract the .BAR Files in next Version . So , If you are planned to export .BAR Files use Version before 12.2.1.4 .
Related
I've been given an AEM quickstart jar file and license.properties from a client and I'm trying to set up a local dev environment as described here: https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-a-local-aem-development-environment.html?lang=en#install-apache-maven
But on step 6; opening the jar file. This starts a local server and I get this screen:
What "license key" is this expecting? And where do I find that. Nothing in the license.properties supplied seems to work.
Thanks
Assuming fair use of the license, just put the license.properties next to the JAR, AEM will recognize the license during the start up.
As AEM is a licensed product, YOu would require a license to run the local jar file. You should get the jar file from your:
Company Admin
Adobe partner manager
Send an email to spphelp#adobe.com to obtain one on behalf of your company.
How to use it?
Option 1:
YOu can place the license.properties file next to the aem-quickstart.jar file and when you run the jar file automatically it should take it.
Option 2:
In the case of MAC sometimes the license.properties file does not recognize even if you placed it next to the AEM JAR file.
In that case
copy the license file to a different folder.
delete the license file from the AEM JAR folder
copy below properties from the license file
customer.name >> Customer Name &
downloadId >> license Key
Refer to https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-license-and-installation/td-p/397135 for Adobe communities answer.
How can I recreate the .atr file for a folder in OBIEE?
On the server, the catalog contains a directory, but its corresponding ATR file is missing.
As a result, the folder does not appear in the UI.
It was inadvertently deleted from the file system.
Can I reverse engineer the ATR using another ATR file, or does the Catalog Manager application have a utility to help restore it?
Instead of reverse-engineering the ATR file, let the Catalog rebuild it automatically by re-propagating folder permissions down from a higher folder level in the catalog.
After this, the missing folder (caused by the missing ATR file) will now appear in the BI Catalog.
I have a zip file created using the Export function in Jaspersoft Server V5.5. This zip file contains a catalogue of all reports, input controls, and queries from a development server.
When I try to import the catalogue to V5.5 on my production server by logging in as superuser and going to "Manage > Server Settings > Import", selecting the zip file, and clicking Submit, I receive an "Import Succeeded" message.
When I check the repository however, most of the directories have been created (but not the input control or queries folders) but none of the actual reports, input controls or queries have been imported.
What am I doing wrong? Do I need to modify any of the files within the zip file?
I have a sesame server running deployed in a WildFly 8.2.0 final container.
How can I restrict access to some particular URLs?
I know I have to edit some XML files (deployment descriptor and some other files) but I don't know which files and where to find them.
I figured it out my self.
Step 1:
Open the openrdf-sesame.war with Total Commander or any file archiver. Go the WEB-INF folder and open the web.xml file.
Edit the web.xml file by adding constraints, roles and the login-config tag as in this example : http://www.rivuli-development.com/further-reading/sesame-cookbook/basic-security-with-http-authentication/
Save the edited file within the archive and redeploy the openrdf-sesame.war file containing the modified web.xml file.
Step 2:
Go to the WildFly folder and enter the bin directory and run the add-user.bat file.
Choose b) Application User and hit Enter.
Enter a username and a password for the new user.
When you are asked "What groups do you want this user to belong to?", type in one of the roles you have created in the web.xml file and hit Enter.
When asked “is this new user going to be used for one AS process to connect to another AS process?” type “yes” and hit Enter.
And that's all.
You now have youre particular URL's restricted.
I am trying to automate deployments of a particular project and a bit lost as to who to handle config file as well as user assets.
(Application is based on Zend Framework based btw).
Main application folder is structured as follows:
./app
./config.ini <----- config file
./modules
./controllers
./models
./views
./libs
./public
That config file is where all the configs are stored.
So 'app' folder contains whole bunch of code in PHP and 'public' contains whole bunch of code in JavaScript, HTML/CSS and stuff like that(web accessible basically).
If I follow Capistrano's model, where each package is expanded into it's own folder that is then symlinked to, how do I handle that config.ini file?
What about all the user content that is uploaded into ./public folder?
Thanks!
The Capistrano approach to this is to have a structure like this on your remote server:
releases/
20100901172311/
20101001101232/
[...]
current/ (symlink to current release)
shared/
in the shared directory you include your config file and any user generated content (e.g. shared/files). Then on each deployment, once you've checked out the code you automatically create symlinks from the checkout into your relevant shared directories. E.g.:
releases/20101001101232/public/files -> shared/files
releases/20101001101232/application/configs/config.ini -> shared/config.ini
that way, when a user uploads a file to public/files it is actually being stored in shared/files.