Documentation

##### WSO2 WSAS 2.2-RC1

- Release Notes
- Contents
- Home

##### Downloads

- Releases

##### Documentation

- User Guide
- FAQs
- Installation Guide
- Source
- Running Behind a Proxy
- Data Services Guide
  - RDBMS Data Source
  - CSV Data Source
  - Excel Data Source
  - JNDI Data Source
- EJB Guide
- Clustering Guide
- JMX Guide
- XKMS Guide
- Changing Keys

##### Samples

- Chad
- Commodity Quote
- Data Services
- Flickr
- Javascript
- Jaxws
- JiBX
- Mtom
- STS
- Trader
- Tiny URL
- Metadata Exchange
- WS-Transfer
- XML Key Managment Specification
- Cluster Management

##### API Documentation

- Java Docs

##### Tools

- Code Generation
- Change Password
- Eclipse IDE Integration
- TCP Monitor
- WSDL2Code
- WSDL View
- Try It
- AAR Validation
- MAR Validation

##### Resources

- News

##### Get Involved

- Mailing Lists
- Integration

##### Project Information

- Project Team
- Issue Tracking
- License

[Download] | [Documentation Home] | [Release Note]

# Frequently Asked Questions(FAQs)

1. Some views of the Management Console are garbled for me. Why and how do I avoid this?
2. Management console sometimes gives me an alert saying "Access Denied. Please Loging First". Why?
3. Why do I see two endpoints listed for my service in the Service Information Page?
4. When a module is uploaded WSO2 WSAS asks me to restart the server. Why is this necessary ?
5. I cannot monitor the messages using the tracer! What's wrong?
6. How can I configure WSO2 WSAS to use persistentRM?
7. How can I change WSO2 WSAS SSL certificate?
8. How do I run WSO2 WSAS as a Unix daemon?
9. On Sun Solaris, when I start WSO2 WSAS, I get a security exception. How do I rectify this?
10. When I start WSO2 WSAS, I get a security exception. How do I rectify this?
11. How do I run WSO2 WSAS behind an Apache HTTPD proxy server?
12. How to Set up the JAVA_HOME Environment Variable on Windows?
13. How do I disable the WSAS console when I deploy it on my production server?

Q1: Some views of the Management Console are garbled for me. Why and how do I avoid this?
A1: WSO2 WSAS 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 WSO2 WSAS supported browser would solve your problem.

Q2: Management console sometimes gives me an alert saying "Access Denied. Please Loging First". Why?
A2: The admin console HTTP session has been set to time out in 30 minutes for security reasons.

Q3: Why do I see two endpoints listed for my service in the Service Information Page?
A3: Default behaviour of WSO2 WSAS 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 WSO2 WSAS asks me to restart the server. Why is this necessary ?
A4: Modules represent significant functionality changes to the system and hence the WSO2 WSAS 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 WSO2 WSAS to use persistent RM?
A6: Change the value of the property in the axis2.xml named "Sandesha2StorageManager" to 'persistent'.

Q7: How can I change WSO2 WSAS SSL certificate?
A7: Please refer to How To Change WSO2 WSAS Crypto Keys

Q8: How do I run WSO2 WSAS as a Unix daemon?
A8: $WSO2WSAS_HOME/bin/daemon.sh start - Start the daemon
$WSO2WSAS_HOME/bin/daemon.sh stop - Stop the daemon
$WSO2WSAS_HOME/bin/daemon.sh restart - Restart the daemon
In addition, you could do;
cd /etc/init.d
ln -s $WSO2WSAS_HOME/bin/daemon.sh wso2wsas
Now, you could do /etc/init.d wso2wsas [start | stop | restart]

Q9. On Sun Solaris, when I start WSO2 WSAS, I get a security exception. How do I rectify this?
A9. Locate the $JAVA_HOME/jre/lib/security/java.security file, and go to the section titled "List of providers and their preference orders" in this file. Add a new provider as follows:
security.provider.<n>=org.bouncycastle.jce.provider.BouncyCastleProvider
where n = the location of the provider you just added. e.g. security.provider.8=org.bouncycastle.jce.provider.BouncyCastleProvider

Q10. When I start WSO2 WSAS, I get a security exception. How do I rectify this?
A10. Here is one possible fix. Locate the $JAVA_HOME/jre/lib/security/java.security file, and go to the section titled "List of providers and their preference orders" in this file. Add a new provider as follows:
security.provider.<n>=org.bouncycastle.jce.provider.BouncyCastleProvider
where n = the location of the provider you just added. e.g. security.provider.8=org.bouncycastle.jce.provider.BouncyCastleProvider

Q11: How do I run WSO2 WSAS behind an Apache HTTPD proxy server?
A11: Please see Running Behind a Proxy Server

Q12. How to Set up the JAVA_HOME Environment Variable on Windows A12. Please follow the instructions to set up the JAVA_HOME environment variable in your computer. First locate the installation folder of the Java development kit (JDK) in your machine. Let us assume it is installed in the folder "C:/j2sdk1.4.2"

1. Right-click on the My Computer icon on your desktop and then click Properties.
2. Click the Advanced tab.
3. Click Environment Variables.
4. Under System Variables, click New.
5. In the Variable name field, enter JAVA_HOME.
6. In the Variable value field, enter the installation path of the Java Development Kit.
7. Click OK.
8. Click Apply Changes.

Q13. How do I disable the WSAS console when I deploy it on my production server? A13. Follow these steps to disable the Management Console

1. Locate WSO2WSAS_HOME/conf/server.xml
2. Locate the following section in the above file
   `<!--
   Functions related to the Management Console
   -->
   <Management>
   <!--
   Enable the Management Console, true/false
   -->
   <EnableConsole>true</EnableConsole>
   </Management>
   `
3. Change the "EnableConsole" entry to "false"
4. Restart WSO2 WSAS
5. Try to access the management console just to verify that it has been disabled. You should see the following message on your browser:
   `Management Console has been disabled. Enable it in the server.xml and try again.`