In the Name field, enter the name that you will call the application in AlwaysUp.
We have specified Derby Network Server but you can specify another name if you like.

Click over to the Logon tab and enter the user name and password of the account in which you installed Derby.
Derby should run in this account so that it can find its settings, java, etc.

Click over to the Startup tab and check the Ensure that the Windows Networking components have started box.
This informs AlwaysUp that Derby needs the network to do its work.

It is best to use stop Derby by running the stopNetworkServer.bat script. To set that up, move to the Extras tab, check the
Use this special command to stop the application box and fill in the path to the batch file in Derby's bin folder.

Click the Save >> button. In a couple of seconds, an application called Derby Network Server will show up in the AlwaysUp window.
It is not yet running though.

On Windows 8, 7, Vista, Server 2012 or 2008, Derby will be
running in Session 0.
Select Tools > Switch to Session 0 to transport yourself to the austere Session 0 desktop where the Derby Network Server console will be visible:

That's it! Next time your computer boots, Apache Derby Network Server will start up immediately, without anyone needing to log on. Please restart your PC now and test that Derby works as expected after Windows comes back to life.

And please feel free to edit Derby in AlwaysUp to check out the many other settings that may be appropriate for your environment.
For example, send email alerts if it stops, hide the console, boost Derby's priority, etc.

Derby not working properly as a Windows Service?

From AlwaysUp, select Application > Report Activity > Today... to bring up a HTML report detailing the interaction between AlwaysUp and Derby.
The AlwaysUp Event Log Messages page explains the more obscure messages.