Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 214 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Obiee 12.2.1.3 Fresh install and not login in analytics
Dears experts,
I am new to obi and I need to prepare this environment to import rpd files.
Despite new installation of obi 12.2.1.3, I can't login in analytics site.
During the enterprise deployment installation, I created a different user than the system for the domain in system.user and jms.queue.auth.
There is a possibility to login tools without SSO, correct?
regards,
Marcelo Tarquinio
Answers
-
Which steps did you follow for this installation? Did you follow these steps? - https://docs.oracle.com/en/middleware/lifecycle/12.2.1.3/bieig/installing-and-configuring-oracle-business-intelligence.p…
Also, is there any reason why you've installed 12.2.1.3? This version went out of Oracle support a few months ago. 12.2.1.4 is the version that Oracle currently supports.
0 -
Hi Joel,
I follow this documentation:
https://docs.oracle.com/en/middleware/lifecycle/12.2.1.3/biedg/index.html
There was no special reason to install version 12.2.1.3
Thank you for rapid response.
0 -
Marcelo-Tarquinio-Oracle wrote:There is a possibility to login tools without SSO, correct?
Of course, by default there is no SSO in OBIEE. Or, to be precise, there is an internal lightweight SSO which is there only to have a shared session between /analytics and /va.
If you can't login start from the beginning: are all the service up and running? Can you check the security in Weblogic console to find your user and verify its groups and continue to Enterprise Manager to check which application role it has.
And as Joel said: 12.2.1.3 is old. You are doing a fresh install, there must not be reasons preventing you from installing the supported version.
0 -
Gianni,
the environment is OK. 2 Prints for context.
Where can I evaluate and attack permissions and roles?
I installed fmw 12.2.1.3 with local OEM for nexts settings.
0 -
http://adminobiee-vip.saude.gov:7001/console : the local LDAP embedded in Weblogic
http://adminobiee-vip.saude.gov:7001/em : Enterprise Manager where you have mappings between local users/groups and application roles
0 -
Thank you Gianni,
I believe the problem is an incorrect permission not yet set for the correct user.
If you have a documentation with this procedures, send me.
Still, I send prints with user permissions on WLS and OEM
best regards,
Marcelo Tarquinio
0 -
Why did you end up doing 2 different weblogic accounts in the first place?
I have the impression you took the most complicated to install OBIEE instead of doing the "normal" one which is mainly few settings and some next, next, next clicks (or silent install directly).
Mainly if you are new, stick with the normal way of doing things instead of going into "exotic" ways (as it looks like you literally copied commands and paths (using the names of the doc like the "aserver" folder etc.).
Do not complicated yourself things for no apparent reasons.
0 -
I'd say the following: Trash that install. Do a correct install of 12.2.1.4 according to normal install procedures.
0 -
Thank you Cristian.
I realy think do this heheh.
But I can't stop at the same step.
0 -
Why did you end up doing 2 different weblogic accounts in the first place?
In customer, there a culture adopted of OBIEE 11g to create for each person one user to OBI. SSO never was used or cogiteted.
I ended up doing a test and leaving it for possible future evaluations
I have the impression you took the most complicated to install OBIEE instead of doing the "normal" one which is mainly few settings and some next, next, next clicks (or silent install directly).
We need install OBIEE in the enterprise deployment.
Mainly if you are new, stick with the normal way of doing things instead of going into "exotic" ways (as it looks like you literally copied commands and paths (using the names of the doc like the "aserver" folder etc.).
Do not complicated yourself things for no apparent reasons.
I would like to do next, next and finish... But this installation will not serve the customer's intended purpose.
Enterprise deployment that I suppose to install, so right now, there's no other option
Thank you
0
