|
|
Right Java tools for J2EE, Web Service, Grid and more |
| |Home | Products | Documents | Downloads | Purchase | Support | Company | Partners | Contact | |
Here are the messages that you may get on message windows:
This window shows information about the software.
Activate the highlighted task. The action takes effect immediately, regardless of how many SuperScheduler Doer or Talker are running.
Alert email change will not take effect until library reset
Alert email change will not take effect until library reset. New values have been saved in the log database. But will not take effect until library reset or J2EE server restart.
This applications deployed. The information you see is the information from
deployment. You may have to restart your application server to start the
applications, depending your application server.
Application undeployed successfully
This application or EJB has been undeployed successfully.
This is a confirmation message for your action. If you click the Ok
or Yes button, the program will go ahead and complete the action.
Otherwise, the action will be canceled.
Cannot deploy both dowry EJB and example EJB
Deploy both dowry EJB and example EJB is not allowed. You do not need both of them:
If you want deploy a different one, undeploy the other one first.
If you chose Simple Install during installation and you have not changed default database parameters, this prerequisite is already satisfied. Casino example is ready to run on your local machine (localhost).
Change log database parameters to this local installation only
Change log database parameters to this local installation only.
The "local installation" is the instance of your application server on your
local physical machine. If you want new parameters
to be changed on other instances of servers, on other machine, you need to do so for each
installation. You can use
command line tool to do it as well.
< The saved parameters will not be effective nor be seen until next library reset or server restart.
See < Log Database Panel for < related information.
Chore database is directly connected
Chore database is directly connected. The connection is working.
Chore database is NOT directly connected
Chore database is NOT directly connected or the connection is broken.
Close all windows
This warns you that the current log datasource will be closed.
This warns you that the current project and the database connection will be closed.
Please close all Dashboard windows before reset
Please close all PeekPoke windows before doing this operation.
Close other windows before doing this operation
Please close all opened windows before doing this.
Close SuperScheduler window. If this is the first time, click on No to see what is going to happen. If you constantly get errors, you probably have no choice, but to close SuperScheduler. If task database is down, an alert email has been sent to administrator. When the error is fixed, try to reopen SuperScheduler.
Close SuperWatchdog window. If this is the first time, click on No to see what is going to happen. If you constantly get errors, you probably have no choice, but to close SuperWatchdog. If chore database is down, an alert email has been sent to administrator. When the error is fixed, try to reopen SuperWatchdog.
Connect to environment database
Connect to the environment database. In most cases, the environment database
is part of your main database. It may or may not be a separated, independent
database.
If the new connection is successful, it takes effect immediately. If
the new connection fails, it will not affect the current connection.
Context sensitive help may not always work at the beginning for IBM's Java
Context sensitive help may not always work at the beginning for IBM's Java. This happens when IBM's java is used (Websphere requires IBM's Java).
See IBM's Java for workaround.
Would you like to create shortcuts, so you can click on them to run Super?
Shortcuts provide convenience for you. They do not provide any real functionality.
Super is written entirely in Java language. But shortcuts are native programs. If you prefer "pure" Java, answer no.
The database has been connected successfully.
Default database is for demo only, not for Heavy Duty test
The database which comes with Simple Install is for demo only. It is not for heavy duty test or production. It is okay to follow our tutorials or run a few tests. But it is not for massive data or running for a long period. Please use your favorite database. If you need SQL scripts for your favorite database, please contact us.
The task is done successfully.
The EJBs are going to be deployed.
Dowry EJBs are required for the facilities. Sufficient
privilege is required.
Deploy EJB to local single server
Deploy EJB to localhost. The application server must be a single server. If your server is a cluster, please use Deployment facilities, or use the administration console from your application server.
Deploy EJBs from Super to EJB server will take a while, depending on your system configuration and the server. Usually it takes a few seconds. It should not be more than one minute.
Super uses deploy utilities from the server to do this task, so the behavior is server dependent. Sufficient privilege is required.
You can use administration tools of the application server to do the job as well.
The EJBs are going to be deployed.
Example EJBs are examples only. The tours use these example EJBs.
Sufficient privilege is required.
Deployment behavior depends on runtime mode for WebLogic version 6.1
Deployment behavior depends on runtime mode for WebLogic version 6.1.
If it is in production mode, the EJBs will not be automatically available.
You need to make them available manually. See the document from the server
for details.
Deployment may or may not work. You may have to deploy those EJBs manually
Deploy and undeploy use underlying facilities from EJB server packages.
The condition depends on many things: version, service patches... The facilities
may or may not work, especially for remote deploy and undeploy. If they
do not work, you must do them manually. See First
time use needs deploy EJBs MANUALLY for details.
Disable local default log database
When you change your log database from default (HypersonicSQL) to another, the local default log database is no longer needed. So, SuperLogging asks you if you want to disable the local default database. If you answer Yes, you can not run it in the future.
SuperLogging will not delete the data inside the database. If you want to delete the data as well, go to logDatabase directory under installed directory (default AceletSuper) and delete all files.
Directory exists. Over write it?
Directory exists. Do you want to overwrite it?
Directory does not exist. Create it?
Directory does not exist. Do you want to create it?
Do you have write privilege to write under that directory?
Do you want to set database parameters?
This message comes when the log database connection is broken. If it
is due to database problems, you do not need to set database parameters.
You just need to bring the log database up and open Log Database Panel
again to reconnect SuperLogging to the database. If you want to set different
log database parameters, click the YES button. The Log Database Panel
will open.
Entitlement and role changes take effect on restart
Changes for entitlement and role will not take effect until restart of all instances of Super, that is all instances of Super with SuperScheduler and SuperWatchdog GUI window open.
Environment database is directly connected
The environment database is directly connected. The environment database usually is your main business database.
Environment database is not directly connected
The environment database is not directly connected. The environment database usually is your main business database.
Environment file for WebLogic exists
This file (extEnv.cmd for Windows or extEnv.sh) is for setting additional environment variables for WebLogic server, so SuperLoggingLibrary will be on the CLASSPATH when you start WebLogic server. It is important.
If the file was installed from a previous installation of Super, overwrite it. If the file is not created by Super, do not overwrite it. You need to modify it. See WebLogic section in Installation for details.
Note: You may need to manually call this file due to a bug in Weblogic's Configuration Wizard. See WebLogic section in Installation for details.
Environment panels are open. The following panels are read only
Environment panels are open. The following panels are read only.
Exit from the program.
Favorite file exists delete it?
Favorite file exists delete it? When you delete a Webservice registry, the favorite file will not be needed. Probably, you want delete it as well.
The file exists. Do you want to overwrite it?
File saved successfully.
First time use. Add holiday sets
This is your first time to use holiday facilities. You do not have any holiday set. The following panels will help you to set holiday sets from holiday sets which comes with SuperScheduler. Of course, you can always to add, edit or delete them later.
First time use. Needs deploy dowry EJBs
You need to deploy dowry EJBs the first time you use Super. Super is going to do so. This information window is shown only the first time.
If the dowry EJB has already been deployed on the server, you do not need to deploy it again. For example, if you have a central sever and many client machines, only the first client needs to deploy the dowry EJB.
Sufficient privilege is required.
If you cancel this operation and want to
deploy or undeploy them later, then you need to go to
the main menu and click the System menu.
First time use. Needs deploy example EJBs
You need to deploy example EJBs the first time you use Super. Super is going to do so. This information window is shown only the first time.
Example EJBs are examples only. Tours use these EJBs.
Sufficient privilege is required.
If you cancel this operation and want to deploy or undeploy them later, then you need to go to
the main menu and click System menu.
First time use. Needs deploy EJBs MANUALLY
You need to deploy dowry and example EJBs at the first time you use Super MANUALLY. See Deploy Dowry and Example EJBs
for more information.
This information window is shown at the first time only.
Scope is an advanced feature. Please read document before using it. See Scope and Change Scope.
The file exists, do you want to overwrite it?
See SuperComponent Beans
and the Bean
Installation Manager Panel for details.
Installation which is specified is done.
Install SuperLogging library on the server side?
Do you want to install SuperLogging library on the server side?
Install license for server side component
Install license for server side component on this machine. Server side component includes server side library and EJBs. The installation is for this machine only. If you have more than one server, you need to install it on each server.
Install Library License for SuperLogging.
Install server side library. Library is the server side library. It
is required for SuperLogging and SuperEnvironment.
Jars from Websphere embedded messaging may be required
Jar files from Websphere embedded messaging may be required, if you want use its embedded messaging system, especially JMS (Java Message Service) Queue. Those jar files are not on your CLASSPATH. See Jars from Websphere embedded messaging may be required from installation guide for more information.
The Java (JDK) version you use is not the expected one. Super may or may not run properly.
Terminate the working task. See Kill working task for more information.
Leading or tailing space exists
GlobalProperties and GlobalObject are case sensitive and space sensitive.
In your input leading or tailing space exists. If you accidentally created
that space, click Cancel to return, otherwise, click Ok.
This is the license information for the SuperComponent, which is a client side component.
See your license file for installation instructions.
See also: Install License.
LimpidLog versions are not the same may or may not work. Please check
document for compatibility issues
LimpidLog agent version and manager version are not the same. May or may not work. Please check document for compatibility issues.
Log database is directly connected
The log database is directly connected. The connection is working.
Log database is NOT directly connected
The log database is NOT directly connected or the connection is broken.
Local log database is shutting down
The local log database is shutting down. If your server is still running,
it can not communicate with the local log database anymore.
The local log database was started when Super was started.
The local log database is installed when you choose "Simple Install". For
production use, you may want to use a different log database from the local log database.
The local log database has been started.
The local log database is installed when you choose "Simple Install". For
production use, you may want to use a different log database from the local log database.
The log database is working now. You do not need to reconnect it.
Log database parameters are read-only with examples deployed
The log database parameters can not be changed with example EJBs deployed. If you want to use different log database, please undeploy example EJB, then install SuperLibrary on the server and deploy dowry EJB.
The log database parameters are saved on the current server.
Log database reconnected to the server
The log database is reconnected to the server. If there are multi-servers,
the connections between log database and other servers are not touched.
Make sure your J2EE/EJB server is running
Make sure your J2EE/EJB server is running please.
Make Sure Related Windows are Closed
Please close all related windows before doing this operation. Otherwise,
you may get an error later.
This number shows how many occurrences have been modified. The file
has been modified and saved if the number is greater than zero.
Monitoring process has been stopped. You can click the Refresh
button to resume it.
There is no new license added for client components. There is no new license found or existing licenses do not need to be re-installed.
There is no new license.
No record found.
No server machine. Delete this entry?
It is not valid if the server machine field is empty on the Connect
Panel. If you click the Ok button while the server machine field
is empty, you imply to delete this item from the ComboBox list.
One or more files exist. Overwrite them?
One or more files exist. Overwrite them? If you answer Yes, all existing files will be overwritten. Otherwise, the operation will be canceled.
File, files, directory or directories exist. They will be over-written.
Please restart Super to make it effective
Please restart Super (the client) to make it effective.
Portfolio example prerequisite
1. The server side library must be installed: The installer of Super prompted you to do so. You should follow the instructions to install the server side library.
2. The default log database is running with default database parameters:
Portfolio example borrows the default log database for demo. The log database
should be running and parameters (URL, login name and password) should
not be changed.
Proxy is for HTTP mode only, not for native mode.
Reconnect server side library to log database. If the new connection
is successful, it takes effect immediately. If the new connection fails,
it will not affect the current connection.
Redeploy may need to restart Super
If the deployment is a re-deployment or undeploy-than-deploy, you may need to restart Super (the client) if you get an error later when you use them.
Note: if you undeploy the example EJB, which contains SuperLoggingEJB, then deploy dowry EJB, the application server may see them as different versions. It will be similar if you undeploy dowry EJB then deploy example EJB.
Report name exists. Delete old data?
There is a report by the same name existing. Confirm to delete old data
.
Report panels are open. The following panels are read only
Report panels are open. The following panels are read only.
This action sends a request to run the task. A SuperScheduler Doer will pick up the request and run it as soon as possible.
Required modification occurrence
This number shows how many occurrences of modification need to be modified. Nothing has been modified yet. The file is not re-saved.
Re-initialize SuperLoggingLibrary for all instances of SuperLoggingLibrary.
You need to restart the server manually now please to make the installation effective.
Restart server manually now, if your installation is over an existing one
You need to restart server manually now, if your installation is over an existing one. If this is the first time to install super library, you do not need to.
This message comes from the Poke Panel.
When you invoke a remote method of an EJB, the method may return an object representing a value.
If the method does return a value, the value is displayed using the object's toString( ) method. If the object's toString( ) method os not defined for human reading, you may have difficulty to read it.
If the method does not return a value, Super will not show anything.
You have made some changes. Do you want to save them?
Super is saving data for hibernation now.
Save log database parameters for direct connect
Save log database parameters for direct connect. The parameters will be saved on the client side. SuperLoggingLibrary wil not see them.
Save task database parameter to your personal directory.
You need to restart SuperScheduler to make it effective.
Scheduler Panel is open. The following panels are read only
Scheduler Panel, either Doer or Talker, is open. The following panels are read only. If you want to change database settings, close Scheduler panel first.
Scope Change May Or May Not Take Effect Immediately
This situation is complex in nature. See Change
Scope for details.
Scope is Static. Parameters are not editable
The scope is Static. Parameters are not editable. See Change Scope for details.
The Shutdown Panel uses utilities from the EJB Server to shutdown the
server gracefully. The behavior is subject to the server's.
Shutdown default local database
Shutdown default local log database.
Shutdown your server manually now please. Restart your server when the installation program asks you later.
The server has been shutdown successfully.
Start time is too old. Do you want to update it?
The start time of the task is too old. It does not affect run-time. But it may take longer time to update it when you modify the task. Do you want to update it? It is recommended to update it. You need to update it manually.
This message is for tasks which runs frequently, for example, every minute. If you have a task runs every month, you probably will not see this message.
You should stop the current Stress test before launching a real stress test. Otherwise, the current test will get time-out error.
The current test is
a rehearsal, not a real stress test.
Please stop peeking first by clicking the Stop button. You can restart
peeking later by clicking the Refresh button.
The program is successfully installed
The bean is successfully uninstalled
SuperLoggingLibrary license has been installed successfully
SuperLoggingLibrary license has been installed successfully.
Please check and activate it by going to the main menu > System > Module > SuperLogging > About.
When you see the license, it is already activated.
Super (the client) has been installed successfully. Please remember
the installed home directory for future use.
SuperScheduler is based on SuperLogging and other technologies. It requires:
1. Server side library must be installed: The installer of Super prompted you to do so. You should follow the instructions to install the server side library.
2. SuperLogging must be up and running.
Or you provide your own version of LogAgent.
If you are not familiar with these, SuperLogging tour,
EasyEJB tour are good places to start.
Did not find what you are looking for.
Note: the search is against each segment of the log records. The delimiters of segments are not as part of the search.
Suspend the highlighted task. The action takes effect immediately, regardless of how many SuperScheduler Doer or Talker are running.
Task database is directly connected
Task database is directly connected. The connection is working.
Task database is NOT directly connected
Task database is NOT directly connected or the connection is broken.
Task database is working now. You do not need to reconnect it.
Task database reconnected successfully.
The following holidays exits and will not be added
The following holidays exits and will not be added. If you want to replace them, please delete existing ones first.
The following licenses installed
The following licenses are installed for client side components. Note: existing valid licenses will not be re-installed.
The following may or may not be deleted
The following files may or may not be deleted when the system tries
to delete them. The files may be in use at that time. When the program exits,
it will try to delete them again. Please make sure you have sufficient
permission.
The stature of search result.
If the result is partial result, most likely the size of the result is too big, so the registry only gives you part of it.
When you search, you may get zero or more warnings or errors.
This will delete all files under the installed directory
Uninstall Super will delete all the files under the installed directory. The
directory will be empty. If the directory is still there, you can delete it by
hand.
Tail process has been stopped, you can press the Refresh key to
resume it later.
The EJBs are going to be undeployed.
Dowry EJBs are required for the facilities.
Undeploy EJBs from EJB server will take a while, depending on your system configuration and the server. Usually it takes a few seconds. It should not be more than one minute.
The EJBs are going to be undeployed.
Example EJBs are examples only. Tutorial uses these EJBs.
Uninstall the component.
Uninstall will exit super and start uninstallation programUninstall will exit super and start uninstallation program.
Watchdog Panel is open. The following panels are read only
Watchdog Panel, either Doer or Talker, is open. The following panels are read only. If you want to change database settings, close Watchdog panel first.
Working
task is not running on this JVM. Do you want to mark it as LOST?
The working task is not running on this JVM. It may be running on other JVM or other machine. Or it may be running in history. This SuperScheduler can not kill it, but can mark its status as LOST.
When should you mark is as LOST? If the machine or JVM which run the working task and crashed. The real status of the working task is unknown. The status shown will be STARTED for ever. In that situation, you can mark it as LOST and put a closure on it.
Note: If the working task is running somewhere and you mark it as Lost, the status may change to ERROR or DONE later by the working task itself to reflect the real status.
You can run either scheduler doer or talker, but not both on the same Super installation at the same time
You can run either scheduler doer or talker, but not both on the same Super installation at the same time. You can run as many doers and talkers as you like on different computers (different installations) at the same time.
You must add your EJB's stub on your project CLASSPATH
You must add your EJB's stub on your project CLASSPATH. Go to the main menu of JBuilder: Project > Project properties.. > Paths > Required Libraries.
See EJB stubs are needed for details.
You need to shutdown all SuperScheduler and SuperWatchdog for database parameter change
You need to shutdown all instances of SuperScheduler and SuperWatchdog, including command line daemon, for database parameter change. Otherwise, different instances of SuperScheduler and SuperWatchdog may connect to different database and get different data.
You need to shutdown all SuperScheduler and SuperWatchdog for entitlement change
You need to shutdown all instances of SuperScheduler and SuperWatchdog for entitlement change. Otherwise, there may be a conflict between some instances and conflict among GUI components.
You need to include the following on your CLASSPATH when you start your server on SERVER machine
You need to include the following on your CLASSPATH when you start your server on SERVER machine.
You need to include the following to the CLASSPATH when you start your Weblogic servers.
A server side library SuperLoggingLibrary is required. It is installed on the following directory:
For Windows: <weblogic_home>\acelet
For Unix: <weblogic_home>/acelet
You need to include SuperLoggingLibrary on the CLASSPATH when you start WebLogic. For example:
SET WEBLOGIC_CLASSPATH=%WEBLOGIC_CLASSPATH%;%WL_HOME%\acelet
in the file
<weblogic_home>\common\bin\commEnv.cmd (Windows)
WEBLOGIC_CLASSPATH=$WEBLOGIC_CLASSPATH:$WL_HOME/acelet
in the file
<weblogic_home>/common/bin/commEnv.sh (Unix)after WEBLOGIC_CLASSPATH is set.
You need to restart Weblogic server manually after these changes, so the new CLASSPATH will take effect.
You need to manually delete the file
You need to manually delete the specified file.
You need to manually update environment file for Weblogic
Note: You may need to manually modify environment setting files See WebLogic section in Installation for details.
You need to restart the server MANUALLY to make the installation effective
You need to restart the server MANUALLY to make the installation effective. Please do so before using Super.
You need to restart the server to make the deployment effective
The J2EE/EJB server must be restarted after the deployment (deploy and undeploy).
You need to restart JBuilder to make the installation and updating effective
You need to restart JBuilder to make installation and updating effective.
You need to shutdown all SuperScheduler and SuperWatchdog for database parameter change
You need to shutdown all instances of SuperScheduler and SuperWatchdog, including command line daemon, for database parameter change. Otherwise, different instances of SuperScheduler and SuperWatchdog may connect to different database and get different data.