Contribute in GitHub:

Viewing XSLD information in highly available SMS Gateway environments

A highly available SMS Gateway environment might include an eXtreme Scale Liberty Deployment (XSLD) caching server. You can collect logs and trace information to help troubleshoot your configuration. (As of Version 1.0.6.0, the XSLD caching server is deprecated in favor of the Redis caching server.)

Downloading XSLD caching server logs

You can download logs from the XSLD Admin Console. If tracing is enabled in the XSLD cache member, you can also download trace files from the same location.

Go to the Admin Console for the XSLD cache member. You can access the console at the following URL, where endpoint is the endpoint host name or IP.
```
https://<endpoint>:9443/wxsui/dashboard
```
Log in with the xsadmin user name and the password that you specified when you set up XSLD.
Click the person icon, and then go to Settings > Trace and Logging.
Click Download Logs.

Configuring tracing in the XSLD caching server

Log in to the Admin Console for the XSLD cache member where you want to enable tracing.
Click the person icon, and then go to Settings > Trace and Logging.
Under Data Grid Servers Trace, specify the trace setting:
- For all logs specific to SMS Gateway, enter com.ibm.ws.smsgw.* and select ALL from the list.
- For other XSLD trace options, see Trace option components.
Click Save.

Viewing data entries in the SMS Gateway data grid

The XSLD caching server stores the SMS Gateway sessions in a shared cache. By viewing the data entries in the data grid, you can see which SMS Gateway sessions are active.

Log in to the Admin Console where the problem was reported in the SMS Gateway logs.
Go to Data Grids and select SMSGW_GRID. In the navigation, select Data.
In the drop-down list, select the SMSGW_MAP.LUT.O map. Enter your key, or enter * for all entries, and then press Enter.

The data entries in the selected map will be displayed. You can follow these same steps to view the entry in the eviction map.