Admin tool: login.jsp

When we access the admin tool login page login.jsp
we only get an empty page (with just the body html tags)
Nothing else.
The jsp examples in our 9.2 database installation
(not iAS) seem to work OK.
We have made the post-installation tasks as described
in "Installing the Ultra search Middle Tier ... "
Thanks for any hints.
Per Thernquist

I have now found the cause of the problem.
During the installation [in Linux Redhat 7.3]
the file login.uix ends up the the folder
$ORACLE_HOME/ultrasearch/webapp/isearch_admin/control
where the login scripts doesn't find it.
Moving login.uix to the folder
$ORACLE_HOME/ultrasearch/webapp/isearch_admin/include
makes things work OK.
/Per
Thanks for a prompt reply
I have followed the configuration instructions in
the Ultra Search Online Documentation/Part 1/
Installing the U S Middle Tier Component .../
Editing the ultrasearch.properties file
The jserv.log says
java.io.FileNotFoundException: Could not find login.uix
login.uix does exist, in the folder
<oracle home>/ultrasearch/webapp/isearch_admin/control alongside with i.a. login.jsp.

Similar Messages

Admin tool: login.jsp (blank page)

I have a problem similar to a recent posting.
I have a 9i Release 2 database installation, server works, sample jsps work, database is up.
Updated the file $ORACLE_HOME/ultrasearch/webapp/config/ultrasearch.properties with our info.
When I try to access the admin page (http://rockfish:7778/ultrasearch/admin/index.jsp) I get to the login page, but it is blank (html body tags, but nothing to display).
The .class and .java file are created in ultrasearch/webapp/isearch_admin/_pages
Is that right? should they be under htdocs/_pages?
Is single sign-on possibly a source of my problem?
Any help would be greatly appreciated,
John

Hi, John:
Does anybody know how to correctly set "AdminConstants.JSP_SRC_HOME" ? Yes.
in ultrasearch.properties file, you need to set the correct admin.srchome variable ->
"Do not use $ORACLE_HOME for admin.srchome , please enter the real file path"
So your ultrasearch.properties file should look like:
=====================================================
connection.driver=oracle.jdbc.driver.OracleDriver
connection.url=jdbc:oracle:thin:@localhost:1521:swims9i
admin.srchome=C:\\oracle\\ora9i\\ultrasearch\\webapp\\isearch_admin
=====================================================
Here is a webIV note explain this problem in details: (you can also find this note in metalink)
http://webiv/cgi-bin/webiv/do.pl/GET?WwwID=Note.202949.1&List=ARTICLES&ARTICLES.Idx=4
Hope this is a clear,
Cindy

Ias problem in admin tool login.

Hi,
When i try to deploy a 9MB J2EE application on iAS6.0SP2, the process
goes fine, but my iAS Admin tool doesnt work. It gives timeout error.
But if the same application's size is cut down to 7MB, the admin tool
works fine. Can you please suggest me the reason for this?
Thanks and Regards.
shivaram.

Hi,
That was a known bug in iAS-Sp2, which has been fixed in iAS-Sp3.
Sanjeev.
Super-User wrote:
Hi,
When i try to deploy a 9MB J2EE application on iAS6.0SP2, the process
goes fine, but my iAS Admin tool doesnt work. It gives timeout error.
But if the same application's size is cut down to 7MB, the admin tool
works fine. Can you please suggest me the reason for this?
Thanks and Regards.
shivaram.

Restrict OBIEE developers to login into OBIEE admin tool withAdministrator

I have developers with their own id's but with admin role assigned to them and If I remove the admin role from their id's they cannot login into OBIEE via admin tool in online mode to make any changes to the RPD.
Q is) Developers make changes to the rpd file in online mode but at the same time I dont want them to have the admin privileges like making changes to the security/connection pool entries so on. But they can make changes to the presentation layer or business model. If I remove the administrator role from their id's they cannot even open the rpd in online mode i.e they can't even login. How do I give the developers the control they need and at the same time lock down the admin related stuff from changes?
Also they cannot make the changes offline and they need to login and open the rpd online.

Hi,
I think you can resolve this issue, by setting up a different application role for all of your developers (yes, with BIAdministrator privileges too). However, in the .rpd you could restrict the access to this role to the physical layer. Briefly, the steps are below
1. Set up a new application role.
2. In the .rpd Manage Identity -> application roles -> New role -> Properties -> Permissions -> Object Permissions.
3. Set 'No Access' to all of your physical layer objects.
Hope this is what you are looking for.
Thank you,
Dhar

Cant login to admin tool

Hi all
I am using Oracle ultra searc on oracle 9i database
I followed all the intallation and post installations Instrustions and I made the user with the specified role
but always displaying wrong password/username
please somebody help me its very ergent
Mostafa Hashem

Hi
To login in the admin tool you have to enter a valid user/password of the database.
Try with WKSYS, if the database was correctly installed you should be able to login.
Did you check the DB-URL, e.g. in ultrasearch.properties.
Chris

Writing Login.jsp and authenticating a user who have stored in MySql DB

Hi Friends,
My project requirement is: Need to write a login page must send the request to servlet is the user and password avail in mysql db, if yes servlet should forward the home page else error message. Tools i need to use is IDE=eclipse, Server = tomcat, database = MySql
Here is source:
pls tell me where i m wrong.
Login.jsp
<%@ page language="java" %>
<html>
<head>
<title>Login Page</title>
<script language = "Javascript">
function Validate(){
var user=document.frm.user
var pass=document.frm.pass
if ((user.value==null)||(user.value=="")){
alert("Please Enter user name")
user.focus()
return false
if ((pass.value==null)||(pass.value=="")){
alert("Please Enter password")
pass.focus()
return false
return true
</script>
</head>
<body>
<h1>Login
<br>
</h1>
<form name="frm" action="/LoginAuthentication" method="Post" onSubmit="return Validate()" >
Name:
<input type="text" name="user" value=""/><br>
Password:<input type="password" name="pass" value=""/><br>
<br>
<input type="submit" value="Login" />
<input type="reset" value="forgot Password" />
</form>
</body>
</html>
Servlet Code:
LoginAuthentication.java
import java.io.*;
import java.util.*;
import java.sql.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.IOException;
import javax.servlet.ServletException;
import javax.servlet.ServletContext;
import javax.servlet.RequestDispatcher;
import javax.servlet.http.HttpSession;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.util.List;
import java.util.ArrayList;
public class LoginAuthentication extends HttpServlet{
private ServletConfig config;
public void init(ServletConfig config)
throws ServletException{
this.config=config;
//public void init() {
// Normally you would load the prices from a database.
//ServletContext ctx = getServletContext();
// RequestDispatcher dispatcher = ctx.getRequestDispatcher("/HomePage.jsp");
//dispatcher.forward(req, res);
public void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException,IOException{
PrintWriter out = response.getWriter();
String connectionURL = "jdbc:mysql://127.0.0.1/SRAT";
//String connectionURL = "jdbc:mysql://192.168.10.59/SRAT";
//127.0.0.1
//http://localhost:3306/mysql
Connection connection=null;
ResultSet rs;
String userName=new String("");
String passwrd=new String("");
response.setContentType("text/html");
try {
// Load the database driver
Class.forName("com.mysql.jdbc.Driver");
// Get a Connection to the database
connection = DriverManager.getConnection(connectionURL, "admin", "admin");
//Add the data into the database
String sql = "select user,password from login";
Statement s = connection.createStatement();
s.executeQuery (sql);
rs = s.getResultSet();
while (rs.next ()){
userName=rs.getString("user");
passwrd=rs.getString("password");
rs.close ();
s.close ();
}catch(Exception e){
System.out.println("Exception is ;"+e);
if(userName.equals(request.getParameter("user"))
&& passwrd.equals(request.getParameter("pass"))){
out.println("WELCOME "+userName);
else{
out.println("Please enter correct username and password");
out.println("<a href='Login.jsp'><br>Login again</a>");
Deployment Descriptor for TOMCAT
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>
SRAT</display-name>
<welcome-file-list>
<welcome-file>login.jsp</welcome-file>
</welcome-file-list>
<servlet>
<servlet-name>LoginAuthentication</servlet-name>
<servlet-class>LoginAuthentication</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>LoginAuthentication</servlet-name>
<url-pattern>/LoginAuthentication</url-pattern>
</servlet-mapping>
</web-app>
PLS HELP ME.
S. Udaya Chandrika

I too have used the same code but its giving the following error:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Wrapper cannot find servlet class Validation or a class it depends on
     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
     org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
     org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
     java.lang.Thread.run(Unknown Source)
root cause
java.lang.ClassNotFoundException: Validation
     org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387)
     org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233)
     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
     org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
     org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
     java.lang.Thread.run(Unknown Source)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.18 logs.
Apache Tomcat/6.0.18
Please some one help??

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

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

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.

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

How to authorize my Login.jsp file to create LoginContext, deployed in war

I am currently doing a login process and I need to know how to give my Login.jsp file the permission to create a LoginContext. I packaged everything in a war file and deployed it to the server.
Specifically this is the error that I am getting:
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: access denied (javax.security.auth.AuthPermission createLoginContext.studentportal)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:384)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:297)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:247)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:585)
     org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
     java.security.AccessController.doPrivileged(Native Method)
     javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
root cause
java.security.AccessControlException: access denied (javax.security.auth.AuthPermission createLoginContext.studentportal)
     java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
     java.security.AccessController.checkPermission(AccessController.java:427)
     java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
     javax.security.auth.login.LoginContext.init(LoginContext.java:224)
     javax.security.auth.login.LoginContext.(LoginContext.java:403)
     org.apache.jsp.Login_jsp._jspService(Login_jsp.java:55)
     org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:105)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:336)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:297)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:247)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:585)
     org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
     java.security.AccessController.doPrivileged(Native Method)
     javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
note The full stack trace of the root cause is available in the Sun-Java-System/Application-Server logs.
In my code in Login.jsp this is what I have at the top of the page:
<%@ page language="Java" import="portal.*,javax.security.auth.login.*" %>
<%
String s = request.getParameter("loginButton");
if (s != null) {
out.println("The user attempted to login");
String user = request.getParameter("username");
String psw = request.getParameter("psw");
AscCallbackHandler cbh = new AscCallbackHandler(user,psw);
LoginContext ctx;
try {
ctx = new LoginContext("studentportal",cbh);
} catch (LoginException le) {
out.println("Sorry, could NOT create context");
}The admin page tells me that portal is deployed at location:
${com.sun.aas.instanceRoot}/applications/j2ee-modules/portal
My entry in the server.policy file looks like so:
grant codeBase "file:/home/jay/sun/Creator2_1/SunAppServer8/domains/creator/applications/j2ee-modules/portal/WEB-INF/-" {
permission javax.security.auth.AuthPermission "createLoginContext.studentportal";
permission javax.security.auth.AuthPermission "modifyPrincipals";
permission javax.security.auth.AuthPermission "getLoginConfiguration";
Which gives the error shown above
Please help
Message was edited by:
jay_dawg
Placing code tags

java.lang.NoClassDefFoundError: org/jdom/JDOMException
     java.lang.Class.getDeclaredConstructors0(Native Method)
     java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
     java.lang.Class.getConstructor0(Class.java:2671)
     java.lang.Class.getConstructor(Class.java:1629)
     org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1164)
     org.apache.jasper.compiler.Node$UseBean.accept(Node.java:1116)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2213)
     org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2219)
     org.apache.jasper.compiler.Node$Root.accept(Node.java:456)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
     org.apache.jasper.compiler.Generator.generate(Generator.java:3305)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:198)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)and following by this

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

Cannot Connect to new Installation with Admin Tool

Have installed BPC 7.5 SP4 Patch 4 on Windows 2008 64-bit. App/Web Server on one machine, SQL Server 2008 on 2nd machine,
Everything seems fine except access via servername - servername used in all the settings.
When trying to access the Administration to start installing new appsets, connect using ip address in admin tool and login using the software install user but will not verify user name/password.
Does anyone have any idea of the issue?
thanks
Lesley

In that case, I'd suggest you make sure both ethernet ports are unplugged from the RAID, power it off and on, plug a cable directly from a laptop to the RAID, set the IP of your laptop to 169.264.11.11 with subnet mask 255.255.0.0, then do "ping 255.255.255.255" and you should see a response from the IP address used by the RAID.
This question is very common here... there are other threads where I've answered this so I won't clarify further here.

J2EE Admin Tool

Hi all1 i'm working with J2EE Engine version 6.30 but its installed on a remote server, and i want to acces with the J2EE admin tool from mi pc, i have the J2EE admin 6.40 and when i'm trying to connect to the J2EE Engine 1rs gives a wraning: 'Warning: J2EE Engine kernel version is older than the version of Visual Administrator' then it continues with the logon and gives me the following error:
'Error while connecting
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.io.InvalidClassException: com.sap.engine.services.adminadapter.descriptor.ClusterDescriptor; local class incompatible: stream classdesc serialVersionUID = -1045741131628563809, local class serialVersionUID = -7364664042028052650'
I guess it happens because of the version, i dont know.
If so, i wanna know if i can download the J2EE Admin Tool or if somebody can give it to me.
thx
rgds.
Gregory

Hi Ivaylo! thx.
I did just what u are saying to me, and when i'm trying to connect from my local pc to the remote server the logon stops in 99% and in the task running appears the following message:
'Login to Sapcfd.spo.com
Host : Sapcfd.spo.com
User name : G.MAYORGA
Port : 56004
Layer : None
Successful !
I hope u can help me.
thx n rgds.
Gregory

Admin tool: login.jsp

Similar Messages

Maybe you are looking for