# Starting a secured Network Server

Bring up the server, turning on SSL and Java security.

This example uses the customized security policy shown in Sample customized Java security policy file. The command line first brings up the server, turning on SSL and Java Security. It also tells the server that NATIVE credentials will be stored in the `mchrystaEncryptedDB` database. That last directive causes the Database Owner's credentials to be stored when `mchrystaEncryptedDB` is created.

    java -Djavax.net.ssl.keyStore=/Users/me/vault/ServerKeyStore \
    -Djavax.net.ssl.keyStorePassword=secretServerPassword \
    -Djavax.net.ssl.trustStore=/Users/me/vault/ServerTrustStore \
    -Djavax.net.ssl.trustStorePassword=secretServerTrustStorePassword \
    -Dderby.storage.useDefaultFilePermissions=false \
    -Dderby.authentication.provider=NATIVE:mchrystaEncryptedDB \
    -Djava.security.manager \
    -Djava.security.policy=/Users/me/myServer.policy \
    org.apache.derby.drda.NetworkServerControl start -p 8246 \
    -ssl peerAuthentication

Parent topic: Putting it all together
Related concepts
Creating and using a secure database
Stopping the secured Network Server