Is the Application Server Running?

Description

If the Enterprise Server is not running, applications will not be accessible.

Solution

Review the information in Did the Server Start? to
determine if the server is running. The server must be running before a server
application can be accessed.

Was Application Deployment Successful?

Description

An application must be successfully deployed before it can be accessed.

Solution

Check the server's log file:

install_dir/domains/domain1/server.log

Invalid User or Password When Using Don’t
Prompt Option

You are getting the error, Invalid user or password,
but you installed the system with the Don't Prompt option,
so the password should be supplied automatically.

Description

The correct password may not have been specified during installation,
or it may not be passed when the domain is started.

Solution

Check the password in the .asadminprefs file. On
UNIX/Linux systems, it is in the home directory for the user under which the
server was installed. On Windows, it is in C:\\Documents and Settings\\username. The contents look something like this:

AS_ADMIN_USER=admin
AS_ADMIN_PASSWORD=administrator

Administrator User Name or Password Not Known

If you have forgotten the administrator user name, you can find it by
inspecting the .adminprefs file, as described in the section
above, or by inspecting the install_dir/domains/domain1/config/keyfile, where domain1 is the default domain. For a
different domain, substitute its name in the path.

If you have forgotten the administrator password, you will need to create
a new user name-password pair by removing the user name and password, creating
new ones, and restarting the server. (You will not be able to read the password,
because it is encrypted in the keyfile.)

To remove the user name and password completely

Stop the server, if it is currently running.

Change to the appropriate WEB-INF directory;
for example:

install_dir/lib/install/applications/adminapp/adminapp_war/WEB-INF

Comment out the entire <security-constraint\> element
in the web.xml file.

Do not delete the element,
as you will be reenabling it later. This action disables security for command-line
operations.

Note –

The commands will still expect a value for --username (or -u) and --password (or -w).
But these can be dummy values, since the server side does not impose any security.