Q1: Some views of the Management Console are garbled for me. Why
and how do I avoid this?
A1: @server_short_name@ Management Console only supports IE 6.0 and upwards,
Firefox 1.0 and upwards. Since the console is dependent on browser based XSLT
processing it may not appear correctly on other browsers. Switching to a
@server_short_name@ supported browser would solve your problem.
Q2: Management console frequently gives me an alert saying "Your
session has expired. Please log in". Why?
A2: The admin console has been set to time out in 30 seconds for security
reasons.
Q3: Why do I see two endpoints listed for my service in the
Service Information Page?
A3: Default behaviour of @server_short_name@ is to expose a deployed service
in all available transports. This behaviour can be controlled by putting
transport entry in the service.xml.
Q4: When a module is uploaded @server_short_name@ asks me to
restart the server. Why is this necessary ?
A4: Modules represent significant functionality changes to the system and
hence the @server_short_name@ server does not allow the modules to be hot
deployed. The server must be restarted to make the modules active.
Q5: I cannot monitor the messages using the tracer! What's
wrong?
A5: Tracer is a separate service and needs to be activated before any message
can be traced. This can be done through the configuration link in the
Management Console.
Q6: How can I configure @server_short_name@ to use persistent
RM?
A6: Change the value of the property in the axis2.xml named
"Sandesha2StorageManager" to 'persistent'.
Q7: How can I change @server_short_name@ SSL
certificate?
A7: Please refer to How To Change
@server_short_name@ Crypto Keys