Locked user tab on portal

Hi All,
Iam gettin the following error when iam clicking the 'locked user' tab on the portal .
User Management Exception
An exception occurred. Inform your system administrator.
Suggested Options
Look at the log file for the cause of the error
can anybody help me its very urgent.........
Thanks in advance..........

Hi,
You either have DB inconsistencies, or you are on SP14.
There was a problem with SP14 for the empty lock reason with locked user accounts. If on SP 14, it is best to upgrade. You can also run the UME consistency check tool in order to remove any inconsistencies which might cause this problem.
Regards,
Iliyan

Similar Messages

If user locked (backend) then from portal i m not able to send data

If user locked (backend) then from portal i m not able to send data
both user are same in front end and backend.
But once user is unlocked i am able to send data from portal to backend...
Regards
Ruturaj

Hi
Since you are in CUA landscape(as u said portal and r3 user are same) unless and utill you unlock it data will not be process.
[Help|What's the right user to access;
BR
Satish Kumar

How to find list of locked users & unlock them?

Hello,
Is there any method in portal to find the list of locked users? and unlock them.
we can unlock single user at a time.
but if we want to unlock a group of users (for Ex:- 20 locked users), how can we unlock al the 20 locked users?
Thanks in advance,
Vila.

Hi Vila,
Go to user administration -> Identity management
Click on advanced search. Go to account information tab. Check the use account locked field and then click on search. This will give you a list of all the users whose accounts are locked.
Select all the users whose accounts you want to unlock, and then click unlock.
Regards,
Ankit

How to configure security policies like account locking, account expiry in portal application?

Hi All,
Can anybody pls tell me how to configure security policies like account locking,
account expiry in portal application? By default, it has a 30 minutes lock period
after 5 retries. But if I want to set other values or want to unlock account of
a user, then what to do ?
TIA,
Sudarson

I have read the SSO admin guide, and performed the steps for enabling SSL on the SSO, and followed the steps to configure mod_osso with virtual host on port 4443 as mentioned in the admin guide.
The case now is that when I call my form (which is developed by forms developer suite 10g and deployed on the forms server which is SSO enabled) , it calls the SSO module on port 7777 using http (the default behaviour).
on a URL that looks like this :
http://myhostname:7777/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=.......
and gives the error :
( Forbidden
You don't have permisission to access /sso/auth on this server at port 7777)
when I manually change the URL to :
https://myhostname:4443/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=.......
the SSO works correctly.
The question is :
How can I change this default behaviour and make it call SSO on port 4443 using https instead ?
Any ideas ?
Thanks in advance

TLN missing for users in Federated Portal Network Setup

Hello All,
We are facing a weird problem in our Federated portal Production setup; when the users login to portal they are not able to see the TLN. On further investigating we found that this issue is happening when the user id is locked in any of the producer portals within our FPN environment due to which the users are not able to view roles related to other systems as well in which there id is active.
This issue is reproducable but only occur once the ID are locked and password is expired in one of the assigned system.
Our FPN setup is as below:
Consumer C connects to Producers
1. A (RDL)
2. B (RDL) - BI Dual Stack
3. D (RRA) - BI Dual Stack
In turn A (producer) connects to 4 ECC systems (F3, M1, R1, R5)
We are using RRA and RDL both in our environment.We have connected all federated portal with P4 Port, so if required we
can use RDL.
Please note our consumer C is EHP1 SP5 and both BI systems B and D are EP 7 sp13.
Any help in this regard is highly appreciated as this is critical issue affecting users in our production environment badly.
Regards,
Priyanka

Hello,
This was an SAP bug. We raised an OSS message and it is taken care now. User now gets TLN and then portal runtime error if the id is locked.
Regards,
Priyanka

User Assignment in Portal

Hi,
I am trying to assign a user in the BI system to a user in the portal (all other steps of BI-EP integration have been done).
After I Iog in to the portal and go to iView User Management, I am not able to find User Mapping option anywhere.
I am having the admin rights for this system and the EP version is 7.
Please can anyone guide where I can find user mapping option or if there is any other way to do so.
Thanks,
CD

hi,
If you have configured SSO using tickets then u dont have to do any mapping for the system.
If you want SSO to be acheived using UserMapping:
Go to you BI system->open permissions->Add your user or group-> Dont forgot to CHECK end user checkbox-->save
Go to User Administation->select the group or user->In bottom details of the User or Group will be opened --> System Mapping Tab from left hand corner -->> assign the username and password of BI for that User of Group.
Regards
Parth
==**Points will be appreciated===

How to create 'Tab page' portal?

Hi,
The 'Portal' configuration page provides 3 types 'Dashboard', 'Standalone Portal' and 'Tab Page Portal'. According to help document, to add new 'Tab Page', needs to ask customer support. Does anyone know how to use 'Tab Page Portal'?
Regards,
Desmond
Edited by: user783168 on 23-Oct-2012 19:02

Similar to Patch 8608149 for 'User Portal' tab on User Transaction in FW 2.2 (default in 2.3.1)?
Follow How To Create A New Multi-Tab Portal Using Configuration Tools (Doc ID 1356225.1)

How to enable create user option in portal under user administration?

Hi,
In Portal, in user administration tab, always the create user and Copy to New user option is disabled, how can i enable those?
-Siva

If the AS ABAP is your datasource for your users there is NO WAY you can create users in the portal UME.
● If the UME has read-only access, you cannot modify user attributes stored in the ABAP system, like first name and last name. You can modify attributes stored in the UME database, like street. Even if read-only access is assigned, users can still change their own passwords.
● If the UME has read-write access, you can create users using the tools of the J2EE Engine. Users created in this way are stored as users in the ABAP system. Extended user data that cannot be stored in the standard ABAP user record is stored in the database of the UME.
in the read/write access the users are created only in the ABAP side and not the java. If you have the read access you cannot create users in the abap side. hence you need the SAP_BC_JSF_COMMUNICATION role to create users in the AS ABAP.....
Trust me .......bottomline ....you cannot create users in the JAVA UME if you have AS ABAP as your datasource !!!!
hope this helps..
\m/

How to use IAS Portal's users in Instant Portal

Is it possible to give access in Instant Portal pages to IAS Portal's users already existing in OID ?
Since I have already the IAS Portal users and I want to give them access to Instant Portal , why not to reference them when defininf Instant Portal pages.
If this is possible, please tell me how to do that .
Thanks in advance .

Yes you can by adding them to oip_available_users Group. The users in this group are eligible for Oracle Instant Portal priviledges. You can grant the oip_available_ user the apppropiate priviledge level for the OIP from the Manage User Rights Screen.
Note: to add IAS Portal user to the oip_available user group in oracle portal:
Go Administer Tab-->Services--->Directory Adminstration--->Groups---do % and click on: Go--->select oip_available_users radio button-->Click on View/Manage Tab-->edit tab--->add User Tab-->submit
Message was edited by:
user523589

Server unlocks locked users automatically - why ?

Hello,
I am using WLS 6.1 SP1
I have set Lockout Enable option to TRUE in Password tab of security.
I also have set
Lockout Threshold = 3
Lockout Duration=999999
Lockout ResetDureation= 5
and rest are default.
After invalid login in a span of 5 minutes, server locks the user.
I can see the status on the console server->Monitoring->Security tab
Total User Unlocked = 0
Locked Users = 1
But if try to login again with same (locked) user with or without correct
password,
the server unlocks user. Next attempt with correct password, user will be
successfully authenticated.
If you see in the console for server->Monitoring->Security tab,
Total User Unlocked = 1
Locked Users = 0
I have not used any unlock command.
Is there is anything wrong in the configuration or web.xml ?
Thanks
Deepak

Hello,
I found out one problem - Looks like a BUG
If Lockout Duration = 999999 then Server unlocks locked user automatically
during next login attempt
with correct or incorrect password.
This looks like a bug becuase
--- Value 999999 is the maximum value allowed and it accepts this value.
In the documentation, this value represented in terms of Seconds as the unit
of measurement
whereas actaully the <Lock Notice> is displayed in terms as 999'999 Minutes.
I tried with value 99999 (5 digits), it works !!!
Regards
Deepak
"Deepak Rampoore" <[email protected]> wrote in message
news:3C43A75F@mail...
Hello,
I am using WLS 6.1 SP1
I have set Lockout Enable option to TRUE in Password tab of security.
I also have set
Lockout Threshold = 3
Lockout Duration=999999
Lockout ResetDureation= 5
and rest are default.
After invalid login in a span of 5 minutes, server locks the user.
I can see the status on the console server->Monitoring->Security tab
Total User Unlocked = 0
Locked Users = 1
But if try to login again with same (locked) user with or without correct
password,
the server unlocks user. Next attempt with correct password, user will be
successfully authenticated.
If you see in the console for server->Monitoring->Security tab,
Total User Unlocked = 1
Locked Users = 0
I have not used any unlock command.
Is there is anything wrong in the configuration or web.xml ?
Thanks
Deepak

Need details about "Lock Profiling" tab of JRockit JRA

Hi,
I'm experimenting with the JRockit JRA tool: I think this is a very useful tool ! It provides very valuable information.
About locks ("Lock Profiling" tab), since JRockit manages locks in a very sophisticated manneer, it enables to get very important information about which monitors are used by the application, helping for improving the performances.
Nevertheless, the BEA categories (thin/fat, uncontended/contended, recursive, after sleep) are not so clear. A short paper explaining what they mean would greatly help.
Fat contended monitors cost the most, but maybe 10000 thin uncontended locks cost the same as 1 fat contended lock does. We don't know.
So, there is a lack of information about the cost (absolute: in ms, or relative: 1 fat lock costs as N thin locks) of each kind of monitor. This information would dramaticaly help people searching where improvements of lock management are required in their application.
Thanks,
Tony

great explanation! Thanks
"ihse" <[email protected]> wrote in message
news:18555807.1105611467160.JavaMail.root@jserv5...
About thin, fat, recursive and contended locks in JRockit:
Let's start with the easiest part: recursive locks. A recursive lock
occurs in the following scenario:synchronized(foo) { // first time thread takes lock
synchronized(foo) { // this time, the lock is taken recursively
}The recursive lock taking may also occur in a method call several levels
down - it doesn't matter. Recursive locks are not neccessarily any sign of
bad programming, at least not if the recursive lock taking is done by a
separate method.
The good news is that recursive lock taking in JRockit is extremely fast.
In fact, the cost to take a lock recursively is almost negligable. This is
regardless if the lock was originally taken as a thin or a fat lock
(explained in detail below).
Now let's talk a bit about contention. Contention occurs whenever a thread
tries to take a lock, and that lock is not available (that is, it is held
by another thread). Let me be clear: contention ALWAYS costs in terms of
performance. The exact cost depends on many factors. I'll get to some more
details on the costs later on.
So if performance is an issue, you should strive to avoid contention.
Unfortunately, in many cases it is not possible to avoid contention -- if
you're application requires several threads to access a single, shared
resource at the same time, contention is unavoidable. Some designs are
better than others, though. Be careful that you don't overuse
synchronized-blocks. Minimize the code that has to be run while holding a
highly-contended lock. Don't use a single lock to protect unrelated
resources, if that lock proves to be easily contended.
In principle, that is all you can do as an application developer: design
your program to avoid contention, if possible. There are some experimental
flags to change some of the JRockit locking behaviour, but I strongly
discourage anyone from using these. The default values is carefully
trimmed, and changing this is likely to result in worse, rather than
better, performance.
Still, I understand if you're curious to what JRockit is doing with your
application. I'll give some more details about the locking strategies in
JRockit.
All objects in Java are potential locks (monitors). This potential is
realized as an actual lock as soon as any thread enters a synchronized
block on that object. When a lock is "born" in this way, it is a kind of
lock that is known as a "thin lock". A thin lock has the following
characteristics:
* It requires no extra memory -- all information about the lock is stored
in the object itself.
* It is fast to take.
* Other threads that try to take the lock cannot register themselves as
contending.
The most costly part of taking a thin lock is a CAS (compare-and-swap)
operation. It's an atomic instruction, which means as far as CPU
instructions goes, it is dead slow. Compared to other parts of locking
(contention in general, and taking fat locks in specific), it is still
very fast.
For locks that are mostly uncontended, thin locks are great. There is
little overhead compared to no locking, which is good since a lot of Java
code (especially in the class library) use lot of synchronization.
However, as soon as a lock becomes contended, the situation is not longer
as obvious as to what is most efficient. If a lock is held for just a very
short moment of time, and JRockit is running on a multi-CPU (SMP) machine,
the best strategy is to "spin-lock". This means, that the thread that
wants the lock continuously checks if the lock is still taken, "spinning"
in a tight loop. This of course means some performance loss: no actual
user code is running, and the CPU is "wasting" time that could have been
spent on other threads. Still, if the lock is released by the other
threads after just a few cycles in the spin loop, this method is
preferable. This is what's meant by a "contended thin lock".
If the lock is not going to be released very fast, using this method on
contention would lead to bad performance. In that case, the lock is
"inflated" to a "fat lock". A fat lock has the following characteristics:
* It requeries a little extra memory, in terms of a separate list of
threads wanting to acquire the lock.
* It is relatively slow to take.
* One (or more) threads can register as queueing for (blocking on) that
lock.
A thread that encounters contention on a fat lock register itself as
blocking on that lock, and goes to sleep. This means giving up the rest of
its time quantum given to it by the OS. While this means that the CPU will
be used for running real user code on another thread, the extra context
switch is still expensive, compared to spin locking. When a thread does
this, we have a "contended fat lock".
When the last contending thread releases a fat lock, the lock normally
remains fat. Taking a fat lock, even without contention, is more expensive
than taking a fat lock (but less expensive than converting a thin lock to
a fat lock). If JRockit believes that the lock would benefit from being
thin (basically, if the contention was pure "bad luck" and the lock
normally is uncontended), it might "deflate" it to a thin lock again.
A special note regarding locks: if wait/notify/notifyAll is called on a
lock, it will automatically inflate to a fat lock. A good advice (not only
for this reason) is therefore not to mix "actual" locking with this kind
of notification on a single object.
JRockit uses a complex set of heuristics to determine amongst other
things:
* When to spin-lock on a thin lock (and how long), and when to inflate it
to a fat lock on contention.
* If and when to deflate a fat lock back to a thin lock.
* If and when to skip on the fairness on a contended fat lock to improve
performance.
These heuristics are dynamically adaptive, which means that they will
automatically change to what's best suited for the actual application that
is being run.
Since the switch beteen thin and fat locks are done automatically by
JRockit to the kind of lock that maximizes performance of the application,
the relative difference in performance between thin and fat locks
shouldn't really be of any concern to the user. It is impossible to give a
general answer to this question anyhow, since it differs from system to
system, depending on how many CPU:s you have, what kind of CPU:s, the
performance on other parts of the system (memory, cache, etc) and similar
factors. In addition to this, it is also very hard to give a good answer
to the question even for a specific system. Especially tricky is it to
determine with any accuracy the time spent spinning on contended thin
locks, since JRockit loops just a few machine instuctions a few times
before giving up, and profiling of this is likely to heavily influence the
time, giving a skewed image of the performance.
To summarize:
If you're concerned about performance, and can change your program to
avoid contention on a lock - then do so. If you can't avoid contention,
try to keep the code needed to run contended to a minimum. JRockit will
then do whatever is in its power to run your progam as fast as possible.
Use the lock information provided by JRA as a hint: fat locks are likely
to have been contended much or for a long time. Put your effort on
minimizing contention on them.

Execute Webdynpro4Abap Application with same ERP-User for all portal-users?

Hi,
is it possible to let a Webdynpro4Abap application run with only one ERP-User for all portal-users? Therefore not needing an ERP-license for every portal-user?
Somekind of mapping maybe?
Regards
Jan

Jan,
It is possible but it all depends on the type of application .If you want to show same data for all users you can use one user but if data is different for all users then you cannot go with this approach.
to configure single backend user for your application go to tcode SICF and look for that application and go to logon data tab by double clicking and give one common user details
Thanks
Bala Duvvuri

Locking users

Hi ,
I want to upgrade support package in my portal.
I don't want anyone to work on the portal while i'm upgrading the support package.
I want to know if it is possible to lock all users - and how do i do it.
I don't want to lock users one by one but lock everyone in 1 click.
i'm running enterprise portal 6.40.
Regards,
Moshe

Hi,
If you want to upgrade the Portal System, I would suggest you stop the portal server and do an upgrade on it. Anyways, while upgrading the J2EE engine, it would stop the server and start it once again and secondly, when you don't expect any user to work on it meanwhile, why not shut down the server ?
Regards,
Sunil

To add custom user attributes in portal user details

Hi,
I am looking at the possibility of adding custom user information attributes in User details of Portal User. By default there are few tabs provided ( general, account info, contact info, additional information.....). I am planning to have another extra tab (custom tab with some custom fields ) to be developed and accessible through external application. My data source would be AS database.
Not necessary that the custom fields to be visible in the UI. but should be manipulated programatically.
Request inputs on feasibility and also the approach that could be followed.
TIA,
-Naresh

Hi,
Follow the link:
http://help.sap.com/saphelp_nw70/helpdata/EN/44/0316d50bbe025ce10000000a1553f7/frameset.htm
This explains the process of adding the custom attributes in user admin.
Thanks,
Rajani

Tab Page Portal

Can any one explain me the steps to create new Tab Page Portal ?
The requirement is to add additional tab in Premise Page similar to the adjustment approval tab page portal on adjustment page.

Similar to Patch 8608149 for 'User Portal' tab on User Transaction in FW 2.2 (default in 2.3.1)?
Follow How To Create A New Multi-Tab Portal Using Configuration Tools (Doc ID 1356225.1)

Locked user tab on portal

Similar Messages

Maybe you are looking for