LDSTechForumProjects

SSO Simulator Getting Started

Note: For previous versions see this SSO Simulator Getting Started Guide.


Prerequisites

Java Development Kit: Version 1.5 or later

Steps to get SSO Simulator working in your development environment

1. Change your hosts file

If you are online when testing, then localhost.lds.org is already defined in DNS and you don't need to make any changes. Skip to the next section. If you are testing offline you need to keep reading here. In order for the cookies to be set properly by the SSO Simulator you will need to modify your hosts file to point a domain name to your computer. In the example configuration files below we use localhost.lds.org as our local domain name. You can choose any name you wish; just make sure that you choose something that will not block another site you need to visit. If you want to work off-line, add the following line to your hosts file following the directions for your operating system below:

127.0.0.1      localhost.lds.org

Windows: edit the hosts file with Notepad (Windows 7 users will need to start Notepad as an administrator) found in:

c:\Windows\system32\drivers\etc\hosts

Linux or OS X: from the command line run the following command to edit the hosts file:

sudo vi /etc/hosts

2. Download the Executable Jar File

Download the latest version of the executable Jar file from the SSO Simulator Downloads page.

3. Create configuration files that meets your needs

Go to the Configuration File Documentation to learn about more advanced features and download sample configuration files.

4. Starting the Simulator from the Command Line

java -Xmx128m -jar SSOSim-7.0.jar <path to config file>

This starts the simulator limiting its memory to 128MB. Previously on this page the command above included another flag, -server, which will run the java vm in a special "optimized" mode that takes longer to start but may run faster[1]. For local development this is probably unnecessary.

Note that if you are using a computer with OS X or Linux, you will need to admin/root privileges to start your SSO Simulator because it is starting on a port lower than 1024. If you get a permission denied error when starting your SSO Simulator try the following command line instead:

sudo java -Xmx128m -jar SSOSim-7.0.jar <path to config file>

You will then be prompted to enter the admin/root password. Once you successfully enter the admin/root password the SSO Simulator will start.

See also: Stopping the Wamulator

This page was last modified on 10 March 2014, at 12:31.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.