I installed Admin Console

 

Issue to Look At

SSL Not Configured correctly

I think most people would have checked and confirmed the following:
1)SSL works,
2)the default server is started in WebSphere administrators Console,
3)the fully qualified domain name was used in the URL,
4)aliases set correctly in the default_server's list, etc.etc.
I noticed that snoop servlet wasn't working anymore. It had been
working before installation of WCS.

According to postings on the Websphere Application Server newsgroup,
the IBM HTTP Server plug-in, is the go-between between the browser and
application server, and during its installation makes certain entries
in the httpd.conf file. When installing Websphere Application server,
you are prompted to select the plug-in. You can choose between IBM
HTTP or Apache plug-in. Be sure to select the plug-in that you
require (in my case- IBM HTTP). However, ensure that the IBM HTTP
Server and IBM HTTP Administration services are turned off before
installing WAS, otherwise the entries cannot be written to httpd.conf
- and thus the whole problem, that the 404 Not Found error results.

After reinstalling it in this way, followed by the fixpacks, efixes,
etc. snoop servlet was working again. Then installed WCS, created and
instance, and successfully loaded: http:\\<fully qualified host
name>\adminconsole, store services and accelerator.


Please note that when entering e.g. http:\\<fully qualified host
name>\adminconsole, you are redirected to
https://<fqhn>/webapp/wcs/tools/servlet/ToolsLogon?XMLFile=adminconsole.Adm­inConsoleLogon
-> note the https


The entry in httpd.conf (at the very bottom), is:
# Page to display indicating the Administration Server is not
installed
<files apadminred.html>
ErrorDocument 404 /9ainterim.htm
</files>
Alias /IBMWebAS/ "C:/ibm/was/web/"
NcfAppServerConfig BootFile
C:\ibm\was\properties\bootstrap.properties


Not too sure exactly what it does, but it wasn't there when
adminconsole wasn't working, or rather, once it was in the http.conf
file, then adminconsole worked.


Also,ensure that this line:
LoadModule ibm_app_server_module C:/ibm/was/bin/mod_ibm_app_server.dll
also appears int http.conf - I think it is also related to the HTTP
server plug-in.

 

 

Link for accessing admin console:

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/txml_command.html

Server Configuration files

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/txml_command.html

Backup and restore administrative configuration files

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/txml_command.html

 

Start Server


linux:/opt/IBM/WebSphere/Express502/AppServer/bin # ./startServer.sh server1
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/Express502/AppServer/logs/server1/startServer.log
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 2188
linux:/opt/IBM/WebSphere/Express502/AppServer/bin #

 

Stop Server

linux:/opt/IBM/WebSphere/Express502/AppServer/bin # ./stopServer.sh server1
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/Express502/AppServer/logs/server1/stopServer.log
ADMU3100I: Reading configuration for server: server1
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server server1 stop completed.

Test Server
linux:/opt/IBM/WebSphere/Express502/Express/bin # ./testServer.sh
.
.
========== Starting Server ==========
.
Wait for the open for e-business message, then press any key to continue.
.
.
.
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/Express502/AppServer/logs/server1/startServer.log
ADMU3100I: Reading configuration for server: server1
ADMU3028I: Conflict detected on port 7880. Likely causes: a) An instance of
the server server1 is already running b) some other process is
using port 7880
ADMU3027E: An instance of the server may already be running: server1
ADMU0111E: Program exiting with error:
com.ibm.websphere.management.exception.AdminException: ADMU3027E: An
instance of the server may already be running: server1
ADMU0211I: Error details may be seen in the file:
/opt/IBM/WebSphere/Express502/AppServer/logs/server1/startServer.log
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
.
.
Press any key to continue.

.
.
.
.
========== Gathering Server Status ==========
.
.
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/Express502/AppServer/logs/server1/serverStatus.log
ADMU0500I: Retrieving server status for server1
ADMU0508I: The Application Server "server1" is STARTED
Press any key to continue.

linux:/opt/IBM/WebSphere/Express502/Express/bin # ./testServer.sh

 

Command line tools

Command line tools are simple programs that you run from a command prompt to perform specific tasks. Using the command line tools, you can start and stop application servers, check server status, add or remove nodes, and complete similar tasks. The command line tools provided with Application Server 5.0 are restricted for use on a single local node.

All of the command line tools are Java programs that use the same Application Server 5.0 administration APIs as the console and the wsadmin tool, which are discussed in the next section. The following is a partial list of some of the command line tools available with Application Server 5.0. A complete list of the command line tools is available in the Application Server 5.0 InfoCenter.

Tool name Description
startServer Launches a new server JVM or writes a script file to launch the server.
stopServer Sends a stop request to the server.
startNode (stopNode) Launches (stops) the node agent process.
startManager (stopManager) Launches (stops) the deployment manager.
addNode Federate an independent node into a cell.
removeNode Remove a node from a cell.
syncNode Ensure that the configuration for a node matches that in the master cell repository.
backupConfig (restoreConfig) Make (restore) a snapshot backup of an Application Server 5.0 configuration.
dumpNameSpace Show the contents of the name space.
EarExpander Expand an EAR file into separate files on the disk.
serverStatus Check whether the servers on this node are running or not.

Most of the command line tools print a usage syntax statement if you invoke them with the help option (by entering either -? or -help as part of the command). Most command line tools also log their activity under the logs directory for the product. All command line tools require authentication data when product security is enabled.