Portal Admin Tool & order of Authentication Providers

For our app, we use two LDAP authentication providers that point to different LDAP
repositories.
Both of them have been configured to have the JAAS flag - OPTIONAL. When the order
is ProviderA and ProviderB (in WLS Console), the authentication works in Portal
Admin Tool. But when the order is reversed to ProviderB and ProviderA, it throws
profileNotFound error and the Portal Admin Tool bombs.
Since both of the providers have been configured to OPTIONAL, shouldn't the order
of the providers be immaterial?
Is this a problem with the Portal Administration Tool?
Thanks,
James

Is this a different problem, then? The ProfileNotFound exception comes only
after
authentication succeeds. If you are on SP2, it makes me wonder if the
credentials
for weblogic are in both providers and are different (different password)?
Also, can you tell me which authorizer and role mapper providers you are
using?
-Phil
"James Spencer" <[email protected]> wrote in message
news:[email protected]...
>
Phil,
We are on SP2. The problem I am having is, the weblogic admin user -weblogic
- is not able to authenticate in Portal Admin Tool depending upon theorder of
the providers.
I thought the authentication for Multiple providers should work in SP2,irrespective
of the order.
I read about the users/groups page works only for the first auth provider.
James
"Phil Griffin" <BEA> wrote:
You're right, the order should be immaterial. The problem is the
portal admin tools (and runtime profile location) rely on a
userExists() call succeeding against a single (default) ATN provider.
There is a number of ways to specify which provider this is - see Javadoc
for getProviderMBean for a description.
http://edocs.bea.com/wlp/docs81/javadoc/com/bea/p13n/usermgmt/RealmHelper.h
tml#getProviderMBean
>>
Better yet, SP2 includes a fix which automatically allows all providers
to
be
checked. The Portal Admin tools still only operate against a singledefault
provider
(to edit users/groups), until SP3.
-Phil
"James Spencer" <[email protected]> wrote in message
news:[email protected]...
For our app, we use two LDAP authentication providers that point todifferent LDAP
repositories.
Both of them have been configured to have the JAAS flag - OPTIONAL.When
the order
is ProviderA and ProviderB (in WLS Console), the authentication worksin
Portal
Admin Tool. But when the order is reversed to ProviderB and ProviderA,it
throws
profileNotFound error and the Portal Admin Tool bombs.
Since both of the providers have been configured to OPTIONAL, shouldn'tthe order
of the providers be immaterial?
Is this a problem with the Portal Administration Tool?
Thanks,
James

Similar Messages

SSO between Portal Application and Portal Admin Tool

Hi All,
We have a requirement for implementing SSO between a Portal application and
Portal admin tool.
We are using WL Portal 8.1 SP4.
Here is the reason for this requirement -
A user logged-into Portal Application needs to login to Portal Admin tool to
do some admin activity. We want to provide a link in the portal application
using which the user can directly login to the Portal Admin tool without
having to enter the credentials again.
If someone has any info on how to implement this, can you please point me in
the right direction.
Thanks,
~Deepak

Hi,
When creating PP you have 2 options
PP used for compiling and PP used for Building
You create PP with all the libraries into Developing/Compiling Other DCs
And another PP with all the libraries into can be packaged into other build results (SDAs).
Once you have these 2 PP in place you add the DC as used DC.
And this should resolve the issue.
Hope this helps.
Cheers-
Pramod

Portal Admin tools passwords

i recently had a database failure and when i restored it, the portalTools page would no longer accept the default username "adminsitrator" and password "password." Any ideas on how restore this or gain alternat access?

Sasikanth,
Usually before you switch UME to AD, you would read it with an LDAP web compliant browser, to check if you could access your OU, Group, and Users. Are you sure you can read the complete LDAP structure on AD?
Kindly re-check the process, to see if you missed out on any steps.
http://help.sap.com/saphelp_erp2004/helpdata/en/cc/cdd93f130f9115e10000000a155106/frameset.htm
Check note 772620 - UME 4.0: Create Groups on Microsoft Active Directory Server
Regards,
James

Weblogic Portal 7.0 to iPlanet Authentication

I have a lot of questions, but first, I will tell you about our problem and our
setup. We are trying to use iPlanet as our Authentication piece for WLP 7.0,
and we are running into problems and exceptions. First, we setup iPlanet to have
a group called Administrators, and included in that group we have several users.
One user, "portalmgr" is the same person who logs in into the Weblogic server
in our portal domain. We also have a test user with a uid of "friedmana" (that's
me, Andy Friedman). After iPlanet was setup, we tried to configure our portal
domain through the console to use iPlanet for authentication. We tried at different
times in the CompatibilityRealm, and then in MyRealm (setting that to the default),
using the console to "Create new iPlanet Authenticator". We set this Authenticator
to Required and the default Authenticator to optional, set the principal to "uid=portalmgr,ou=People,dc=gd,dc=com",
we set the credential, we set the User Base DN, and we set the Group Base DN.
The rest of the settings we left as default. As a side note, I think we set
all those correctly because we did this with a regular WLS domain and it seemed
to work ok. When we restart the server, we can login to the server, the console,
the portal we created, and the Portal Administrative Tools with the portalmgr
user. We can login to the console with any of our Administrator users that we
created in iPlanet. However, in Portal App Tools, we cannot see our portal under
Portal Management. We also cannot see any other users that we created in iPlanet
in the Users section of Portal Admin Tools (although we got that to work with
one of our configurations, but that gave us a bunch of other problems). When
we try to create a new user through our portal, that user gets created (and we
can see him in the Portal App Tool), but he cannot login. We cannot see that
created user in iPlanet (are we supposed to be able to?). We think we are authenticating
to some degree through iPlanet because the default access to the PortalAppTools
(administrator/password) does not work anymore, but one of our created users (portalmgr)
does work. And when I try our other created user (friedmana), it seems to login
but then tells me I have a license problem. We have not written any code or modified
the config file, but according to the way the Authenticator is configured in the
WLS 7.0 docs, it doesn't appear that you need to.
So here are some of my many questions:
1) In a recent message on this newsgroup, Scott Dunbar said this "WLP 7.0 uses
a compatibility realm only and will not work with the custom realm that you created
for the Netscape directory server. " So is that true? Should we ignore "myRealm"
when using a Portal domain?
2) In that same message Scott also listed some coded to add to config.xml. Is
this relevant to our situation? Part of the reason I ask is that Scott wrote
this to a guy who was trying to create a custom realm and we are not. Here is
that code: <CachingRealm BasicRealm="myRealm" CacheCaseSensitive="true" Name="wlcsCachingRealm"/>
<CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));
user.dn=ou=people,dc=beasys,dc=com; server.principal=uid=dirmanager,ou=people,dc=beasys,dc=com;
membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames)); group.filter=(&(cn=%g)(objectclass=groupofuniquenames));
server.host=somehost.beasys.com; group.dn=ou=groups,dc=beasys,dc=com" Name="myRealm"
Password="your_password_here" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
3) If this code is necessary, then can we still set up the iPlanet Authenticator
using the console, the way we set it up for WLS 7.0?
4) If we have to use the Compatibility Realm, does that mean we need to do any
configuration in the "Compatibility Security" section of the console?
5) I thought the Compatibility Realm had to do with previous versions (6.X) of
Weblogic...why would we have to use it for Portal 7.0?
6) Why does the Portal 7.0 documentation refer to WLS 6.1 documentation for Configuring
the LDAP Security Realm (http://edocs.bea.com/wlp/docs70/dev/security.htm Configuring
An LDAP Server for Intrgration)?
We tried quite a few things and got some nasty stack traces that we couldn't figure
out, but I didn't want to mention everything we tried and all of our exceptions
unless you need it in order to help us.
Thanks,
Andy Friedman

Please see answers inline.
Andy Friedman wrote:
I have a lot of questions, but first, I will tell you about our problem and our
setup. We are trying to use iPlanet as our Authentication piece for WLP 7.0,
and we are running into problems and exceptions. First, we setup iPlanet to have
a group called Administrators, and included in that group we have several users.
One user, "portalmgr" is the same person who logs in into the Weblogic server
in our portal domain. We also have a test user with a uid of "friedmana" (that's
me, Andy Friedman). After iPlanet was setup, we tried to configure our portal
domain through the console to use iPlanet for authentication. We tried at different
times in the CompatibilityRealm, and then in MyRealm (setting that to the default),
using the console to "Create new iPlanet Authenticator". We set this Authenticator
to Required and the default Authenticator to optional, set the principal to "uid=portalmgr,ou=People,dc=gd,dc=com",
we set the credential, we set the User Base DN, and we set the Group Base DN.
The rest of the settings we left as default. As a side note, I think we set
all those correctly because we did this with a regular WLS domain and it seemed
to work ok. When we restart the server, we can login to the server, the console,
the portal we created, and the Portal Administrative Tools with the portalmgr
user. We can login to the console with any of our Administrator users that we
created in iPlanet. However, in Portal App Tools, we cannot see our portal under
Portal Management. We also cannot see any other users that we created in iPlanet
in the Users section of Portal Admin Tools (although we got that to work with
one of our configurations, but that gave us a bunch of other problems). When
we try to create a new user through our portal, that user gets created (and we
can see him in the Portal App Tool), but he cannot login. We cannot see that
created user in iPlanet (are we supposed to be able to?). We think we are authenticating
to some degree through iPlanet because the default access to the PortalAppTools
(administrator/password) does not work anymore, but one of our created users (portalmgr)
does work. And when I try our other created user (friedmana), it seems to login
but then tells me I have a license problem. We have not written any code or modified
the config file, but according to the way the Authenticator is configured in the
WLS 7.0 docs, it doesn't appear that you need to.
So here are some of my many questions:
1) In a recent message on this newsgroup, Scott Dunbar said this "WLP 7.0 uses
a compatibility realm only and will not work with the custom realm that you created
for the Netscape directory server. " So is that true? Should we ignore "myRealm"
when using a Portal domain?Answer 1) yes, in Portal 7.0 the CachingRealm BasicRealm cannot be myRealm
2) In that same message Scott also listed some coded to add to config.xml. Is
this relevant to our situation? Part of the reason I ask is that Scott wrote
this to a guy who was trying to create a custom realm and we are not. Here is
that code: <CachingRealm BasicRealm="myRealm" CacheCaseSensitive="true" Name="wlcsCachingRealm"/>
Answer 2) You have two choices in Weblogic 7.0 and 6.1 for Portal 4.0 or
7.0 LDAP Realms. Either configure the LDAP V1 Realm (Deprecated) or
create a Custom Realm for LDAP V2 Realm support. If you select LDAP V2
Realm support you should use the entries that are found in Weblogic's
6.1 config.xml or as specified in their documentation. There you will
find a custom realm entry that may be used for Netscape/iPlanet. The
LDAP V2 Realm has some enhancements that should increase communication
performance because of added filtering capability (amoung other things).
>
<CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));
user.dn=ou=people,dc=beasys,dc=com; server.principal=uid=dirmanager,ou=people,dc=beasys,dc=com;
membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames)); group.filter=(&(cn=%g)(objectclass=groupofuniquenames));
server.host=somehost.beasys.com; group.dn=ou=groups,dc=beasys,dc=com" Name="myRealm"
Password="your_password_here" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
3) If this code is necessary, then can we still set up the iPlanet Authenticator
using the console, the way we set it up for WLS 7.0?Answer 3) You can set up the realms through the console. However I've
found it easier to debug problems with LDAP V2 Realm setup by editing
config.xml directly. Primarily because the configurationData parameter
can be a tricky line to edit through the small console box. The
parameter needs to be one long line without carraige returns and in some
places spaces.
4) If we have to use the Compatibility Realm, does that mean we need to do any
configuration in the "Compatibility Security" section of the console?Answer 4) That would be the place to edit Portal LDAP Security yes.
5) I thought the Compatibility Realm had to do with previous versions (6.X) of
Weblogic...why would we have to use it for Portal 7.0?Answer 5) Portal 7.0 is using the same implementation of realms
available in 6.x.
6) Why does the Portal 7.0 documentation refer to WLS 6.1 documentation for Configuring
the LDAP Security Realm (http://edocs.bea.com/wlp/docs70/dev/security.htm Configuring
An LDAP Server for Intrgration)?
Answer 6) see Answer 5)
>
We tried quite a few things and got some nasty stack traces that we couldn't figure
out, but I didn't want to mention everything we tried and all of our exceptions
unless you need it in order to help us.Use the CustomRealm entry from your posting. Make sure
ConfigurationData is one long line and remove spaces.
>
Thanks,
Andy Friedman

Portal admin URL via www server

Hi,
We are using the portal admin web tool located in the http://localhost:7001/xxxAdmin
The portal shows up and usable perfectly. However I would like to use it via webserver. The webserver redirects my URL to the http://localhost:7001/xxxAdmin.
So my request->http://xxx.com/xxAdmin is redirected to http://localhost:7001/xxxAdmin.
Login page shows up perfectly. I try to log in and the URL is broken. http://localhost:7001/xxxAdmin/login/login.do shows a page not found. Of course on the web there is no localhost.
How can I avoid this redirect? Or how can I hardcode the URL to use? I understood that the beehive-url-template.xml is for similar purpose but what is the template url name that the portal admin tool is using? Any other solution?

Suresh -
1. To deploy without Workshop/Eclipse, you will generally create an EAR of your application (via the Export Wizard under the File > Export menu) and deploy that with either the WLS console, WLST, or the weblogic.Deployer utility class. http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14245/deployment.htm#i1027718 has a fair amount of information.
2. The WLP admin portal is a webapp deployed as part of your application, via the wlp-tools-admin-app-lib.ear shared library. So, its host and port number are the same as wherever you deploy your application. The url path of the admin portal is controlled via your application's META-INF/weblogic-application.xml file; there's a <wls:library-context-root-override> element for the 'tools' context-root.
3. Since the WLP admin portal is a webapp deployed as part of your application, it needs to have a unique context-root to support deploying multiple WLP applications. The ear wizard in Eclipse defaults to specifying the context-root as [appname]Admin to support this, but you can always change the context-root as I described above.
4. No, currently, the WLP admin console is application-scoped and controls the configuration and behavior for that application. So, for multiple applications, you will have to use multiple admin console urls.
Greg

Admin tool acl FileRealm error

i deployed my own portal admin tool on a custom domain and enterprise app. i can
pull up the admin tool menu, but none of buttons function properly. i get the
following errors:
<Feb 11, 2002 6:43:06 PM CST> <Info> <EJB> <EJB Exception during invocation from
home: [email protected]0be7e threw
exception: java.lang.ClassCastException: weblogic.security.acl.internal.FileRealm
java.lang.ClassCastException: weblogic.security.acl.internal.FileRealm
furthur down in the trace....
Exception[com.bea.portal.admin.AdminResourceSystemException: EJB Exception: :
Exception[com.bea.portal.admin.DelegatedAdminSystemException: EJB Exception: :
java.lang.ClassCastException: weblogic.security.acl.internal.FileRealm at com.bea.p13n.usermgmt.internal.GroupManagerImpl.isMember(GroupManagerImpl.java:770)
can anyone please provide some insight into possible resolutions or interpretation
of the above errors. i have an administrator user assigned to the SystemAdministrator
group. i do not know what else i am missing though.
thanks,
sam

these errors only occur when accessing the "User Management" or "Portal Management"
buttons. the other 3 buttons work fine.
-sam
"sam" <[email protected]> wrote:
>
i deployed my own portal admin tool on a custom domain and enterprise
app. i can
pull up the admin tool menu, but none of buttons function properly.
i get the
following errors:
<Feb 11, 2002 6:43:06 PM CST> <Info> <EJB> <EJB Exception during invocation
from
home: [email protected]0be7e
threw
exception: java.lang.ClassCastException: weblogic.security.acl.internal.FileRealm
java.lang.ClassCastException: weblogic.security.acl.internal.FileRealm
furthur down in the trace....
Exception[com.bea.portal.admin.AdminResourceSystemException: EJB Exception:
Exception[com.bea.portal.admin.DelegatedAdminSystemException: EJB Exception:
java.lang.ClassCastException: weblogic.security.acl.internal.FileRealm
at com.bea.p13n.usermgmt.internal.GroupManagerImpl.isMember(GroupManagerImpl.java:770)
can anyone please provide some insight into possible resolutions or interpretation
of the above errors. i have an administrator user assigned to the SystemAdministrator
group. i do not know what else i am missing though.
thanks,
sam

WLP 10 & using portal admin console portlets

Hi,
i need te reuse existing portlets from the portal admin tool.
I found the following code from edocs but i need some clarifications
about it. What is a ResourceID ? How can i get it ?
Thx
Emmanuel
// Create a resource ID (see Javadoc)
final ResourceID resourceID = ... ;
// Get a TreeSelectListener
final HttpServletRequest request = ...;
final HttpServletResponse response = ...;
final PortletORB portletORB = PortletORB.getPortletORB(request, response);
final PortletHandle portletHandle = portletORB.getBroadcastPortletHandle();
final TreeSelectListener listener = portletHandle.
narrow(TreeSelectListener.class);
// Call selected(...)
final ResourcePath resourcePath = new ResourcePath(new ResourceID[] {
resourceID });
final ResourceType resourceType = resourceID.getResourceType();
listener.selected(resourcePath, resourceType, resourceID);

Hi, I even get this error but with the app running in WLS8.1 SP5. Any pointers.

RDBMS Authenticator and Portal Admin

In WLP 8.1, I created a RDBMS Auth and I can see the list of
users/groups in the Weblogic Console. The Portal Admin's user/group
page does not show any users except those authenticated by
DefaultAuthenticator.
Why is Portal Admin not showing the users ? In the previous version any
custom auth (federated or non) showed the users/groups list on Portal
Admin page. Where is the secret switch to add custom auths to the
Portal Admin ?
Is jad'n the only way to work with BEA's products ?

For porting purposes, setting RDBMSAuth as # 1 (per Docs/Greg) and
adding weblogic/portaladmin::Administrators/PortalSystemAdministrators
does the needful.
Gregory Smith wrote:
Bhupi -
Thanks for the feedback. We have been looking at this issue specific to
the portal services for managing users/groups. I'll forward this message
onto the team looking into this.
Greg
Bhupi wrote:
Thanks Greg.
Replacing the following element within the Security element in
config.xml with RDBMS Auth should solve the problem but the default
users/groups have to be in RDBMS (weblogic/portaladmin/...).
<weblogic.security.providers.authentication.DefaultAuthenticator
Name="Security:Name=myrealmDefaultAuthenticator"
Realm="Security:Name=myrealm"/>
The following use-case should be supported out-of box.
If I change the default to RDBMS or LDAP, it should get the
weblogic/portaladmin from the Default (the export dat from embedded
LDAP listed them) if it does not find it in the custom ones.
HOW >> Since the Security Providers can be stacked, a federated
authenticator which should be the default, consider's the
AuthenticationProvider's list instead of individual authenticators.
<weblogic.management.security.Realm
AuthenticationProviders="Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter|Security:Name=myrealmTwicsAuthenticator"
I know this is another requirement but will make things much easier,
specially for UUP scenarios.
Gregory Smith wrote:
Bhupi -
The portal User/GroupManager services (which the admin portal
utilizes) currently only support 1 Authenticator, generally the
first, most-capable Authenticator listed. That's why you're seeing
only the DefaultAuthenticator users and groups in the admin portal.
There is some information about this in the upgrade guide
(http://e-docs.bea.com/wlp/docs81/upgrade/index.html) under the
Compability Domain chapter. More documentation is planned for in the
coming months to better explain this.
Greg
Bhupi wrote:
In WLP 8.1, I created a RDBMS Auth and I can see the list of
users/groups in the Weblogic Console. The Portal Admin's user/group
page does not show any users except those authenticated by
DefaultAuthenticator.
Why is Portal Admin not showing the users ? In the previous version
any custom auth (federated or non) showed the users/groups list on
Portal Admin page. Where is the secret switch to add custom auths
to the Portal Admin ?
Is jad'n the only way to work with BEA's products ?

Can not access sample & admin tools after configuring Oracle8.1.7

Hi all,
I am using WLS6.1(sp2) and WLPortal4.0(sp1).
I changed the default database(i.e. Cloudscape) to Oracle by following the doc
http://edocs.bea.com/wlp/docs40/deploygd/oraclnew.htm
But, after setting up the Oracle8.1.7, when i try to access the sample stock portal
from the homepage, i am getting the following exception
PortalPersistenceManager: portal 'portal/stockportal' not found
<Feb 20, 2002 12:33:19 PM EST> <Error> <HTTP> <[WebAppServletContext(1467076,stockportal,/stockportal)]
Servlet failed with S
ervletException
javax.servlet.ServletException: Received a null Portal object from the PortalManager.
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.setupPortalRequest(PortalWebflowServlet.java:194)
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(PortalWebflowServlet.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at jsp_servlet.__index._jspService(__index.java:92)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
even i can not access the admin tools.....i get the follwing error when i try
to access the portalTools/index.jsp
<Feb 20, 2002 12:38:18 PM EST> <Warning> <Webflow> <Webflow could not resolve
a destination given: appname [tools], namespace
[admin_main], origin [begin], event [defaultEvent] with request id [3121877];
Attempting to load Configuration-error-page.>
<Feb 20, 2002 12:38:18 PM EST> <Error> <Webflow> <Error while parsing uri /portalTools/application,
path null, query string n
amespace=admin_main - Webflow XML does not exist, is not loaded properly, or you
do not have a configuration-error-page defin
ed.
Exception[com.bea.p13n.appflow.exception.ConfigurationException: The configuration-error-page
node was not found in the webfl
ow xml file. for webapp [tools], namespace [admin_main]. While trying to display
CONFIGURATION ERROR: [Exception[com.bea.p13n
.appflow.exception.ConfigurationException: Bad Namespace - namespace [admin_main]
is not available for webflow execution. Mak
e sure the [admin_main.wf] file is deployed in webapp [tools].]],]
at com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processConfigurationError(WebflowExecutorImpl.java:786)
at com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebflowRequest(WebflowExecutorImpl.java:484)
at com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebflowRequest(WebflowExecutorImpl.java:419)
at com.bea.p13n.appflow.webflow.servlets.internal.WebflowServlet.doGet(WebflowServlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at jsp_servlet.__index._jspService(__index.java:92)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
Am i missing any step here???
can anybody help me????
thanks
Vijay

oops...i missed step5.
it is working now after doing the sync.
thanks
Vijay
"Daniel Selman" <[email protected]> wrote:
Did you sync the applications and load the sample data?
Sincerely,
Daniel Selman
"vijay bujula" <[email protected]> wrote in message
news:[email protected]...
Hi all,
I am using WLS6.1(sp2) and WLPortal4.0(sp1).
I changed the default database(i.e. Cloudscape) to Oracle by followingthe
doc
http://edocs.bea.com/wlp/docs40/deploygd/oraclnew.htm
But, after setting up the Oracle8.1.7, when i try to access the samplestock portal
from the homepage, i am getting the following exception
PortalPersistenceManager: portal 'portal/stockportal' not found
<Feb 20, 2002 12:33:19 PM EST> <Error> <HTTP><[WebAppServletContext(1467076,stockportal,/stockportal)]
Servlet failed with S
ervletException
javax.servlet.ServletException: Received a null Portal object fromthe
PortalManager.
atcom.bea.portal.appflow.servlets.internal.PortalWebflowServlet.setupPortalReq
uest(PortalWebflowServlet.java:194)
atcom.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(PortalWe
bflowServlet.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
atweblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:241)
atweblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at jsp_servlet.__index._jspService(__index.java:92)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
even i can not access the admin tools.....i get the follwing errorwhen i
try
to access the portalTools/index.jsp
<Feb 20, 2002 12:38:18 PM EST> <Warning> <Webflow> <Webflow could notresolve
a destination given: appname [tools], namespace
[admin_main], origin [begin], event [defaultEvent] with request id[3121877];
Attempting to load Configuration-error-page.>
<Feb 20, 2002 12:38:18 PM EST> <Error> <Webflow> <Error while parsinguri
/portalTools/application,
path null, query string n
amespace=admin_main - Webflow XML does not exist, is not loaded properly,or you
do not have a configuration-error-page defin
ed.
Exception[com.bea.p13n.appflow.exception.ConfigurationException: The
configuration-error-page>> node was not found in the webfl>> ow xml file. for webapp [tools, namespace [admin_main]. While tryingto
display
CONFIGURATION ERROR: [Exception[com.bea.p13n
appflow.exception.ConfigurationException: Bad Namespace - namespace[admin_main]
is not available for webflow execution. Mak
e sure the [admin_main.wf] file is deployed in webapp [tools].]],]
atcom.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processConfigurati
onError(WebflowExecutorImpl.java:786)
atcom.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebflowRequ
est(WebflowExecutorImpl.java:484)
atcom.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebflowRequ
est(WebflowExecutorImpl.java:419)
atcom.bea.p13n.appflow.webflow.servlets.internal.WebflowServlet.doGet(WebflowS
ervlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
atweblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:241)
atweblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at jsp_servlet.__index._jspService(__index.java:92)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
Am i missing any step here???
can anybody help me????
thanks
Vijay

Can't access to Portal Admin Console.

Hi all,
I'm working with WLP 10.2. I've created the ear-file (using maven) and deployed it on server (with Unix-system). The current application works well.
My current task is a creation portal in streaming mode. Unfortunately I can't access to Portal Admin console for resolving task. I always retrieve "Error 404 (Not found)".
As I know the admin-tools.war is responsible for Portal Admin Console. I've checked admin-tools.war is running on server (with status "Active").
I'm using the next path for running Portal Admin Console: {serverhost:port}/{context root of admin-tools}/portal.portal.
Maybe, Should I set up(correct) application.xml or weblogic.xml?
Please let me know if you have any ideas.
Thanks,
Yuriy

I think your URL is wrong, try with the following...
http://{server:port}/{name_your_ear}Admin/portal.portal
name_your_ear= The name of your Enterprise Application.
For example,
http://localhost:7001/DemosEarAdmin/portal.portal
I hope this helps

Visual Admin tool in Read only mode?

HI
is it possible to access the Visual Admin tool in Read only mode. if Yes then How? if No then why?
Regards
Shridhar Gowda

Hi,
check with links, you may get some info, but i am not sure.
Check some VC roles and assign those roles for perticular users for full and read only.
1. http://help.sap.com/saphelp_nw70/helpdata/EN/7a/a0e84240857076e10000000a1550b0/content.htm
2. https://admin.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/659c082e-0c01-0010-2e9f-ac674cfff2d2
3. https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0bf413a-66a6-2a10-8eb7-91b9e99c4a97
Regards,
Srini Nookala
Edited by: Srini Nookala on Aug 26, 2008 4:02 PM

OBIEE : Newly created rpd file not showing in the online mode in Admin tool

Hi,
I have recently installed OBIEE 10.1.3.4.2 and Oracle XE databse in a Windows XP (Professional version 2002 Service Pack 3) virtual machine on my Windows 7 machine.
1) I have create an rpd file in Admin tool (all three layers). But I can only load this rpd file in offline mode, not in online mode.
a)Saved the file sanjay1.rpd in c:\OracleBI\server\Repository directory
b)Updated the c:\OracleBI\server\config\NQSConfig.ini (commented out the existing Star entry and replaced it with Star = sanjay1.rpd, DEFAULT;),
c)Modified the C:\OracleBIData\web\config\instanceconfig.xml and made change to the CatalogPath entry (<CatalogPath>C:/OracleBIData/web/catalog/sanjay1</CatalogPath>)
d)Stopped and restarted OC4J, “Oracle BI Presentation Server” and “Oracle BI Server” services.
But I am still not able to load sanjay1.rpd in the Admin tool in the online mode. It is showing up only in the offline mode. What do I need to do load the file in the online mode.
2)The existing Start entry in NQSConfig.ini was Star = samplesales.rpd, DEFAULT before I updated it. But samplesales.rpd is not showing up in online mode either. When I am selecting File/Open/Online a popup is coming up with title "Open Online AnalyticsWeb" and prompting to enter Administrator password. I would like to know why samplesales.rpd was not showing up in online mode and where is AnalyticsWeb coming from.
Thanks
Sanjay

Dear Muram,
Is did not work.
1)Wihile the servers were running I opened the rpd in offline mode. It displayed the message the file can only be opened in the Read-Only mode. I accepted the message, opened the file and clsoed it and exited from Admin tool. I stopped the 2 services “Oracle BI Presentation Server” and “Oracle BI Server” in that order, and restrated them in the reverse order. In the admin tool it is still showing in the offline mode only
2)I have as such no interest in AnalyticsWeb that is showing in the online mode. I did not create it, it must have been installed along with OBIEE. But I am curious where it is coming from. Because A)There is no rpd file for AnalyticsWeb in the Repository Directory B)Before I edited the NQSConfig.ini the default setting was samplesales.rpd. So AnalyticsWeb was never included in the NQSConfig.ini file C) samplesales.rpd was included in the NQSConfig.ini once, but it never showed up online.
Thanks
Sanjay

Not able to display users from Opneldap in Weblogic 8.1 Portal Admin

Hi
          I had configured openldap for multiple authentication in weblogic 8.1. I am able to see users and groups from openldap in weblogic admin console but when i go to Portal Administration i am not able to see those users and groups. Also as per weblogic documentation it says that Authentication provider selection is shown automatically in Portal Admin. Also i am able to log to portal application from openldap users.
          I want set entitlements using Portal Admin for openldap users
          Can anyone suggest how to make it work.

Hi
          I had configured openldap for multiple authentication in weblogic 8.1. I am able to see users and groups from openldap in weblogic admin console but when i go to Portal Administration i am not able to see those users and groups. Also as per weblogic documentation it says that Authentication provider selection is shown automatically in Portal Admin. Also i am able to log to portal application from openldap users.
          I want set entitlements using Portal Admin for openldap users
          Can anyone suggest how to make it work.

Unable to start admin tool

Hi,
I am newbie to portal.
I have installed weblogic 6.1(sp1) & weblogic portal 4.0. I was unable to start due
to license error. I executed updatelicense.cmd. I can start portal with system/weblogic
password. I am not able to logic in to admin tool with system/weblogic. What is wrong.
Any help is appreciated.
Environment is windows2000.

André is right.
Something I find useful if you are like me and keep forgetting
what user/password and URLs to use, you might want to consider
pointing your browser to the default page for the server: http://localhost:7501
This will forward to the welcome-page of the default web appp and
the page provides links to the differents tools and samples. It also
has a reminder of the username/password combinations on the left hand side.
Michel.
"André Pönisch" <[email protected]> wrote in message news:[email protected]..
Hi,
the admin-login is after the installation "administrator" and "password".
André
[email protected]
www.AP-Home.de

Oracle RAC with Admin tools

Hello!
I use Weblogic Server 10.3.2. I have a portal application and I want to manage the content with Portal Administration Console from admin-tools.war . Admin-tools is a part of my portal application. I eclipse I check for my ear project on Project Facets : Admin Console, Admin Framework, Portal Application Services, Portal Customizations Framework.
I have a cluster with two servers. As a database I use Oracle 10 with two instances : instance 1, instance 2. I have created my domain with wizard and I checked RAC Multidatasources.
All datasources and multidatasources are targeted to my weblogic cluster, also where is deployed my app and Portal Administration Console ( admin-tools.war).
I use the multidatasources :
Multidatasource Name : cgDataSource JNDI:      cgDataSource     Load-Balancing
Oracle Driver for data sources cgDataSource-rac0, cgDataSource-rac1 : oracle.jdbc.xa.client.OracleXADataSource
MultiDataSource Name : cgDataSource-nonXA     JNDI : cgDataSource-nonXA      Load-Balancing     Oracle Driver:
Oracle driver for datasources from multidatasource : oracle.jdbc.OracleDriver . Supports Global Transaction
Name : p13nDataSource
JNDI : p13n.trackingDataSource,p13n.sequencerDataSource,cm.sequencerDataSource,p13n.leasemanager,p13n.dataSyncDataSource,p13n.entitlementsDataSource,p13n.jobManagerDataSource,p13n.quiescenceDataSource,p13n.credentialsDataSource     Load-Balancing
Oracle driver for datasources from multidatasource: oracle.jdbc.OracleDriver .
!!DOESN'T Supports Global Transaction!!
Name: portalDataSource
JNDI : weblogic.jdbc.jts.commercePool contentDataSource contentVersioningDataSource portalFrameworkPool     Load-Balancing
Oracle driver for datasources from multidatasource: oracle.jdbc.OracleDriver .
Supports Global Transaction
Name: portalDataSourceAlwaysXA
JNDI : portalFrameworkPoolAlwaysXA     Load-Balancing
Oracle driver for datasources from multidatasource: oracle.jdbc.xa.client.OracleXADataSource
Name: portalDataSourceNeverXA JNDI: portalFrameworkPoolNeverXA
Oracle driver for datasources from multidatasource: oracle.jdbc.xa.client.OracleXADataSource
But when I try to add a content, after a server restart, I receive the following error :
<Error> <PortalAdminTools> <sun1> <Server-0> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1289472419642> <BEA-415097> <A RepositoryException was thrown: java.sql.BatchUpdateException: ORA-00001: unique constraint (WEBLOGIC_PORTAL_PROD.PK_CM_PROPERTY) violated
com.bea.content.RepositoryException: java.sql.BatchUpdateException: ORA-00001: unique constraint (WEBLOGIC_PORTAL.PK_CM_PROPERTY) violated
     at com.bea.content.internal.server.common.dbaction.Batcher.processWithRetries(Batcher.java:148)
     at com.bea.content.internal.server.common.dbaction.Batcher.processAnyRemainingItems(Batcher.java:86)
     at com.bea.content.repo.internal.server.dao.PropertyDao.insert(PropertyDao.java:383)
     at com.bea.content.repo.internal.server.persister.JDBCNodePersister.createNode(JDBCNodePersister.java:148)
     at com.bea.content.repo.internal.server.logic.NodeOpsLogic.create(NodeOpsLogic.java:227)
     at com.bea.content.repo.internal.server.bean.NodeOpsBean.create(NodeOpsBean.java:106)
     at com.bea.content.repo.internal.server.bean.RepoNodeOps_ehgg7y_ELOImpl.create(RepoNodeOps_ehgg7y_ELOImpl.java:323)
     at com.bea.content.repo.internal.client.common.Node.create(Node.java:123)
     at com.bea.content.spi.internal.NodeOpsImpl.createNode(NodeOpsImpl.java:823)
     at com.bea.content.spi.internal.ExtendedNodeOpsImpl.createNodeWithNodeTypeAndObjectClassAndWorkflow(ExtendedNodeOpsImpl.java:81)
     at com.bea.content.federated.internal.delegate.LatestInterfaceVersionWrapper.invoke(LatestInterfaceVersionWrapper.java:72)
     at $Proxy457.createNodeWithNodeTypeAndObjectClassAndWorkflow(Unknown Source)
     at com.bea.content.federated.internal.filter.logging.NOPSLoggingFilter.createNodeWithNodeTypeAndObjectClassAndWorkflow(NOPSLoggingFilter.java:111)
     at com.bea.content.federated.internal.delegate.NodeLogic.createNodeWithType(NodeLogic.java:275)
Caused By: java.sql.BatchUpdateException: ORA-00001: unique constraint (WEBLOGIC_PORTAL.PK_CM_PROPERTY) violated
     at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:629)
     at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:9447)
     at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:211)
     at weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:191)
What is the problem? Please tell me if you need more details about my configuration and problem.

This issue is beyond simple WLS JDBC. I suggest opening a WLS portal bug.

Portal Admin Tool & order of Authentication Providers

Similar Messages

Maybe you are looking for