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

Similar Messages

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

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 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.

JAZN Admin tool - what username and password??

I need to use the JAZN Admin tool that comes with JDeveloper to configure security for the embedded OC4J. I have specified JAAS as the policy provider by adding the following lines to jre/lib/security/java.security:
auth.policy.provider=oracle.security.jazn.spi.PolicyProvider
login.configuration.provider=oracle.security.jazn.spi.LoginConfigProvider
However, I don't know what user name and password to specify when attempting to invoke a JAZN command, such as "java -jar jazn.jar -listusers". What is the default username & password that is included in the JDeveloper 10g installation? Or do I have to manually configure a username/password? If so how?
Thanks in advance!
Steve

See https://forums.adobe.com/thread/1619850

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

Can only see User Management in Admin Tools

I configured an LDAP realm and included the required admin group to access
the Administration Tools. However, the only thing I can see in
Administration Tools is User Management. Why is that?

Wendy,
Would it be possible for you to send us a file from your LDAP directory
server? Please forward this information to the support case you have open.
In the \iPlanet\Servers\slapd-yourhost\config directory.
Send the dse.ldif file.
Basically what we want to do is to compare the user and group dn values
specified in the vlvBase lines with your config.xml. Also grab the
string that starts with creatorsname ... look for something like
creatorsName:
uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot
The principal value in the config.xml will be the creatorsName string.
Set the principal string in config.xml should be something like
Principal="uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot"
unless your iPlanet schema has been changed.
So, in the config.xml LDAPRealm definition explicitly set Group is context.
GroupIsContext="false"
Set the AuthProtocol to simple.
Your config.xml LDAPRealm definition should have 13 fields and look
something like:
<LDAPRealm
AuthProtocol="simple"
Credential="password"
GroupDN="o=beasys.com, ou=Groups"
GroupIsContext="false"
GroupNameAttribute="cn"
GroupUsernameAttribute="uniquemember"
LDAPURL="ldap://myhost.beasys.com:389"
Name="myLdapRealmV1"
Principal="uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot"
SSLEnable="false"
UserAuthentication="bind"
UserDN="o=beasys.com, ou=People"
UserNameAttribute="uid"/>
-- Jim
Wendy Kajiyama wrote:
Hi,
iPlanet 5.0, no service pack.
I got the user and group DN from our Network Admin.
"Jim Litton" <[email protected]> wrote in message
news:[email protected]...
Wendy,
Can you also supply the vendor and version number of your directory
server?
I was looking at your config.xml from your support case and I am
unfamiliar with the user DN and group DN strings you are using.
Where did you find the syntax for those strings? Is that particular
string syntax documented somewhere on the LDAP vendors site?
Jim Litton
Developer Relations
Ture Hoefner wrote:
Hello Wendy,
I suspect a configuration problem in the LDAPRealm, but it is possible
that you have a P13N-only license. That is probably a long-shot because
I
don't know if we sell those any more. You are using Portal 7.0, right?
I can try to help... can you answer these questions:
* which version?
* After you log into as "administrator" (who is a member of
"SystemAdministrator"), can you access the Group Management tools and
see
the "SystemAdministrator" group and the list of users who belong to that
group?
* Do the all of the users and groups that you see match what you have
in
your LDAP server?
"Wendy Kajiyama" <[email protected]> wrote in message
news:[email protected]...
Hi Ture,
Thanks for your reply. Unfortunately, after contacting support and
receiving the patch for LDAP I am still having the problem of not being
able
to see the icons in Admin Tools.
Any other ideas?
Thanks,
wendy
"Ture Hoefner" <replyto@newsgroup> wrote in message
news:[email protected]...
Hi Wendy,
Which version?
After you log into as "administrator" (who is a member of
"SystemAdministrator"), can you access the Group Management tools and
see
the "SystemAdministrator" group and the list of users who belong to
that
group? Does it match what you have in your LDAP server? If you cannot
list
members of groups in your Portal JSP admin tool then contact support
and
ask
for the patch that fully enables WLS's LDAPRealm for use with Portal
(it
is
CR070870 for Portal 4.0, I don't know if there is a patch for 7.0, or
if
it
is included in a SP for 7.0...)
If you are able to list the users in a group then make sure you have
the
group "SystemAdministrator", not "SystemAdministrators".
I've used delegated portal administration with LDAPRealm for 7.0 so I
know
it works. I suspect a configuration issue. I will try to help you
figure
it out.
"Wendy Kajiyama" <[email protected]> wrote in message
news:[email protected]...
yup, i set up LDAP to have the required administrator groups and log
in
the
admin tools as administrator which is a user in the
SystemAdministrator
group.
"kurt c" <[email protected]> wrote in message
news:[email protected]...
could this not be a permissions issue? are you logged in as
'administrator'?
"Wendy Kajiyama" <[email protected]> wrote:
I checked to see if ebusiness.jar was in my application and it's
there.
Any
other ideas?
Thanks!
wendy
"Peter Laird" <[email protected]> wrote in message
news:[email protected]...
Wendy,
You may be seeing CR081150, which is a bug report regarding the
removal
of
ebusiness.jar
from your application. If you remove this JAR, the admin tool
fails
to
load certain
EJBs which cause it to only display more than the user tool. The
workaround is
to put ebusiness.jar back into your applicaiton. If this is
unacceptable,
contact
Support and they will work with you.
Cheers,
PJL
"Wendy Kajiyama" <[email protected]> wrote:
I configured an LDAP realm and included the required admin group
to
access
the Administration Tools. However, the only thing I can see in
Administration Tools is User Management. Why is that?

Starting visual admin tool

HI
I have recently installed SAP ENTERPRISE PORTAL
Now,I need to do some changes in the visual admin tool
I browsed to following loaction in my personal computer where I have installed SAP EP
c:\usr\sap\CE1\J00\j2ee\JSPM
There I See the file go.bat Once I click on that I see blank command prompt window being get displayed.
What are the settings I need to perform inorder to open the VISUAL ADMIN TOOL
Thanks in advance

Hi Rev,
1> Your Visual admin tool is located in folder
"C:\usr\sap\CE1\JC00\j2ee\admin".
JSPM is another tool used for upgrade or appling *.SDA or *.SCA files.
2> There is also web based tool called NetWeaverAdministrator located under alias http://<hostname>:<port no.>/nwa .
3> Also set the path for JAVA_HOME in environment variable.
4> If the locked account is the only administrators account, follow the instructions in note 669848.
5> If you no longer connect to the Visual admin it is better change the password of the user j2ee_admin as mentioned bellow
You have to change the J2EE Engine administrator password in the secure store as follows:
a. Start the Config Tool by executing the /usr/sap/<SID>/<Instance name>/j2ee/configtool/configtool script file.
b. Select secure store.
c. Select the admin/password/<SID> entry.
d. Enter the J2EE Engine administrator user new password in the Value field and choose Add.
e. Choose File -> Apply to save the data.
f. Restart the J2EE Engine
Regards,
Manomeet
Award points if helpful **

Open and connect in OBI 11.1.1.5 admin tool fowwoling OBE Upgrade

I installed OBI11.1.1.5 on Redhat 5.2 and the admin tool on a windows. In this two machine I have OBI 10 server and admin tool installed as well. The OBI 11 components are all up running as I can access them such as EM and represention service.
Following OBEhttp://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3 .I upgraded our 10g rpd and catalog and see the repository saved in instance_home, and verified that the default is RPD sh20110903_BI002.
Next step in the OBE, I verify Reposiotory Metadata. I launched the admin tool, opened inline. In the generated dialog box, I entered the password in defined in the update script as Repository Password, and used weblogic login in User/Password. All other fields are blank. That is all I can do in the dialog box, but the Open buttone is always grey. I think at least one available repository should be listed in the list box at the bottom, but it was empty.
Then I tried to create a new repository. In step 2 Select Data Source, I choose ODBC 3.5 and use a valid system DSN, but got Error : The connection has failed.
I tried also use Connection Type OCI 10g/11g. IN the Data Source Name I used a valid netservice name defined in a Oracle client's Oracle_HOME. But still got Error : The connection has failed.
Questions
1) How can make the Open button active in the Open inline RPD dialog box?
2) Why the valid System DSN failed to connect in 11g admin tool. It is OK in 10g admin tool and ODBC configure
3) How to make Admin Too; sees the tnsnames definition. Should I copy the tnsnames.ora file to somewhere under Admin Tool installation directory?
Many thanks.

Thanks. The post appares make sense. I opened my user.sh file and has 2 questions:
1) There are 32bit section and 64 bit section, and it states that 32 bit server must work with 32 bit client, so is for 64 bit. In my case, the clients are most likely 32 bit windows (browsers and admin tool), but the server is installed on Redhat 64 bit. Is this a problem? How do I know if my OBIEE iis running 64 or 32 bit?
2) All entries in the user.sh file are commented out. Then what file is used to in the current OBI11, it is started automatically after the installation.

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

Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.

          Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
          Acelet is the leader in J2EE tools area. If you google "j2ee tools",
          "j2ee logging", "j2ee scheduler" or alike, you will find Acelet
          is at the top of the result.
          Super 4.00 comes with:
          SuperEnvironment
          SuperLogging
          SuperPeekPoke
          SuperReport
          SuperScheduler
          SuperStress
          and SuperPatrol, as a schedule job.
          The evaluation edition can be anonymously downloaded from:
          http://www.ACElet.com.
          Super is a component based monitor and administration tool
          for EJB/J2ee. It provides built-in functionality as well as
          extensions, as SuperComponents. Users can install
          SuperComponents onto it, or uninstall them from it.
          Super has the following functions:
          * A J2EE monitor.
          * A gateway to J2EE/EJB servers from different vendors.
          * A framework holding user defined SuperComponents.
          * A full-featured J2EE logging and J2EE tracing tool for centralized,
          chronological logging.
          * An EJB tool for Peeking and Poking attributes from EJBs.
          * An EJB Stress test tool.
          * A J2EE global environment tool.
          * A J2EE report tool.
          * A J2EE Scheduler tool.
          * A J2EE Business patrol tool.
          It is written entirely in the Java(TM) programming language.
          The current version support:
          * JOnAS 2.4 and 2.6
          * SunONE 7.0
          * Universal servers.
          * Weblogic 6.1, 7.0 and 8.1
          * Websphere 4.0 and 5.0.2
          * jBoss 3.0 and 3.2
          ********** What is new:
          Version 4.00 November, 2003
          Enhancement:
          1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
          (with/without proxy) protocol mode for SuperEnvironment,
          SuperLogging, SuperReport and SuperScheduler.
          2. SuperLogging 4.00: tracing can work on both live database and retired database.
          3. SuperReport 3.00: works for both live database and retired database.
          4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
          Panel.
          Bug fix:
          1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
          Version 3.00 July, 2003
          Enhancement:
          1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
          scope,
          with enhancements and bug fixes.
          2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
          password.
          Add MenuTreePanel.
          3. Improved GUI and document.
          4. Add support to WebLogic 8.1.
          Bug fix:
          1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
          2. SuperScheduler 2.0: Startup should never be reported as missed.
          3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
          Version 2.20 Jan. 2003
          Enhancement:
          1. Add desktop and start menu shortcuts for MS-Windows.
          2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
          3. SuperLogging 2.40: Add new sendAlarmEmail() method.
          4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
          direct database is not practical; Allow user to choose
          favorite logging software; Add Last day as Monthly
          repeating attribute.
          Change:
          1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
          Bug fix:
          1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
          open Environment Manager.
          2. SuperLogging client 1.52: Annoying exception thrown when you use
          JDK 1.4 (the program runs okay).
          3. SuperPeekPoke 1.61: Fix bug where input object contains
          java.lang.Double and alike.
          4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
          PatrolAlarm for SuperPatrol; Composite task with members;
          Non-scheduled run on other host; Around edges of last
          days in Monthly with holiday policy.
          Version 2.10 July 2002
          Enhancement:
          1. SuperScheduler 1.3: Add Future View to check future schedule in
          both text and Gantt-chart mode.
          2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
          activities.
          3. SuperEnvironment 1.3: uses new graphic package adding print and
          preference facilities.
          4. SuperPeekPoke 1.6: uses new graphic package adding print and
          preference facilities.
          5. SuperStress 1.21: uses new graphic package.
          Bug fix:
          1. SuperStress 1.21: fixed graphic related bugs.
          Version 2.01 June 2002
          Enhancement:
          1. Add options for Look & Feel.
          2. Preference is persistent now.
          Bug fix:
          1. Installation for WebLogic 7.0: extEnv may not be installed on the
          right place, so SuperLibrar on the server side was not loaded and
          causes other problems.
          Version 2.00 June 2002
          Enhancement:
          1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
          when any Doer causes things to change.
          2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
          3. SuperReport 1.2: Support default HTML browser for reading HTML document.
          4. Support WebLogic 7.0.
          5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
          6. SuperEnvironment 1.21: New SuperEnvironment tour.
          Bug fix:
          1. WebSphere Envoy did not always list all JNDI names.
          Version 1.90 May 2002
          Enhancement:
          1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
          2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
          effective period. Add Patrol job type as SuperPatrol.
          3. Add support for both JOnAS and jBoss.
          4. Add more elements on Report criteria.
          Change:
          1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
          and descend.
          2. New log database.
          Bug fix:
          1. Alert email should be sent once in the interval, regarding number of servers
          in the clustering.
          2. Minor bug fixes to make errors handled better on SuperLogging.
          3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
          them.
          4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
          Version 1.80 March 2002
          Enhancement:
          1. Add new component: SuperScheduler
          Bug fix:
          1. SuperLogging: Verbose should ignore class registration.
          2. SuperLogging-tracing: an exception was thrown if the java class without package
          name.
          Version 1.70 January 2002
          Enhancement:
          1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
          weblogic 6.1, need download an application).
          2. Add alias names for log threshold as new Java suggests.
          3. New component: SuperReport.
          Change:
          1. SuperLogging: Log database parameters are specified in a properties file, instead
          of EJB's deployment descriptor. It is more convenient and it avoids some potential
          problems. No change for development, easier for administration.
          Bug fix:
          1. Add Source Path Panel now accepts both directory and jar file.
          2. Bug in SuperEnvironment example (for version 1.60 only).
          Version 1.60 December 2001
          Enhancement:
          1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
          2. Add timeout parameter to logging access.
          3. New installation program with A). Easy install. B). Remote command line install.
          4. Support EJB 2.0 for Weblogic 6.1.
          5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
          was supported since version 1.5).
          Change:
          1. Poke: argument list is set at define time, not invoke time.
          2. Default log database change to server mode from web server mode, booting performance
          to 10-20 times.
          Bug fix:
          1. If the returned object is null, Peek did not handle it correctly.
          2. If the value was too big, TimeSeries chart did not handle it correctly. Now
          it can handle up to 1.0E300.
          3. Help message was difficult to access in installation program.
          4. Source code panel now both highlights and marks the line in question (before
          it was only highlight using JDK 1.2, not JDK 1.3).
          5. Delete an item on PeekPoke and add a new one generated an error.
          Version 1.50 August, 2001
          Enhancement:
          1. Source code level tracing supports EJB, JSP, java helper and other
          programs which are written in native languages (as long as you
          write correct log messages in your application).
          2. Redress supports JSP now.
          3. New installation with full help document: hope it will be easier.
          4. Support WebSphere 4.0
          Version 1.40 June, 2001
          Enhancement:
          1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
          and PieView for GlobalProperties.
          GlobalProperties is an open source program from Acelet.
          2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
          Changes:
          1. The structure of log database changed. You need delete old installation and
          install everything new.
          2. The format of time stamp of SuperLogging changed. It is not locale dependent:
          better for report utilities.
          3. Time stamp of SuperLogging added machine name: better for clustering environment.
          Bug fix:
          1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
          Style Panel may not show up.
          Version 1.30 May, 2001
          Enhancement:
          1. Add ConnectionPlugin support.
          2. Add support for Borland AppServer.
          Version 1.20 April, 2001
          Enhancement:
          1. Redress with option to save a backup file
          2. More data validation on Dump Panel.
          3. Add uninstall for Super itself.
          4. Add Log Database Panel for changing the log database parameters.
          5. Register Class: you can type in name or browse on file system.
          6. New tour with new examples.
          Bug fix:
          1. Redress: save file may fail.
          2. Install Bean: some may fail due to missing manifest file. Now, it is treated
          as foreign beans.
          3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
          on the original file, do not need copy to a temporary directory anymore.
          4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
          Now it pick up all availble ones and give warning messages.
          5. Stress: Launch>Save>Cancel generated a null pointer exception.
          Changes:
          1. installLogDatabase has been changed from .zip file to .jar file.
          2. SuperLogging: If the log database is broken, the log methods will not try to
          access the log database. It is consistent with the document now.
          3. SuperLogging will not read system properties now. You can put log database
          parameters in SuperLoggingEJB's deployment descriptor.
          Version 1.10 Feb., 2001
          Enhancement:
          1. Re-written PeekPoke with Save/Restore functions.
          2. New SuperComponent: SuperStress for stress test.
          3. Set a mark at the highlighted line on<font size=+0> the Source Code
          Panel (as a work-a-round for JDK 1.3).</font>
          4. Add support for WebLogic 6.0
          Bug fix:
          1. Uninstall bean does physically delete the jar file now.
          2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
          Version 1.00 Oct., 2000
          Enhancement:
          1. Support Universal server (virtual all EJB servers).
          2. Add Lost and Found for JNDI names, in case you need it.
          3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
          for Envoys which do not support JNDI list).
          Version 0.90: Sept, 2000
          Enhancement:
          1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
          and alike) as input values.
          2. Reworked help documents.
          Bug fix:
          1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
          further time-out.
          2. MDI related bugs under JDK 1.3.
          Version 0.80: Aug, 2000
          Enhancement:
          1. With full-featured SuperLogging.
          Version 0.72: July, 2000
          Bug fix:
          1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
          Version 0.71: July, 2000
          Enhancement:
          1. Re-worked peek algorithm, doing better for concurent use.
          2. Add cacellable Wait dialog, showing Super is busy.
          3. Add Stop button on Peek Panel.
          4. Add undeploy example button.
          Bug fix:
          1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
          1.2 and 1.3
          Version 0.70: July, 2000
          Enhancement:
          1. PeekPoke EJBs without programming.
          Bug fix:
          1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
          Changes:
          1. All changes are backward compatible, but you may need to recompile monitor
          windows defined by you.
          Version 0.61: June, 2000
          Bug fix:
          1. First time if you choose BUFFER as logging device, message will not show.
          2. Fixed LoggingPanel related bugs.
          Version 0.60: May, 2000
          Enhancement:
          1. Add DATABASE as a logging device for persistent logging message.
          2. Made alertInterval configurable.
          3. Made pace for tracing configurable.
          Bug fix:
          1. Fixed many bugs.
          Version 0.51, 0.52 and 0.53: April, 2000
          Enhancement:
          1. Add support to Weblogic 5.1 (support for Logging/Tracing and
          user defined GUI window, not support for regular monitoring).
          Bug fix:
          1. Context sensitive help is available for most of windows: press F1.
          2. Fix installation related problems.
          Version 0.50: April, 2000
          Enhancement:
          1. Use JavaHelp for help system.
          2. Add shutdown functionality for J2EE.
          3. Add support to Weblogic 4.5 (support for Logging/Tracing and
          user defined GUI window, not support for regular monitoring).
          Bug fix:
          1. Better exception handling for null Application.
          Version 0.40: March, 2000
          Enhancement:
          1.New installation program, solves installation related problems.
          2. Installation deploys AceletSuperApp application.
          3. Add deploy/undeploy facilities.
          4. Add EJB and application lists.
          Change:
          1.SimpleMonitorInterface: now more simple.
          Version 0.30: January, 2000
          Enhancement:
          1. Add realm support to J2EE
          2. Come with installation program: you just install what you want
          the first time you run Super.
          Version 0.20: January, 2000
          Enhancement:
          Add support to J2EE Sun-RI.
          Change:
          1. Replace logging device "file" with "buffer" to be
          compliant to EJB 1.1. Your code do not need to change.
          Version 0.10: December, 1999
          Enhancement:
          1. provide SimpleMonitorInterface, so GUI experience is
          not necessary for developing most monitoring applications.
          2. Sortable table for table based windows by mouse
          click (left or right).
          Version 0.01 November., 1999:
          1. Bug fix: An exception thrown when log file is large.
          2. Enhancement: Add tour section in Help information.
          Version 0.00: October, 1999
          Thanks.

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

Portal Admin tools passwords

Similar Messages

Maybe you are looking for