How to Survive Application Configuration Files, Which are being Copied to the GlassFish Environment in a AS Cluster? (Doc ID 1339918.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle GlassFish Server - Version: 2.1.1 and later   [Release: 2.1 and later ]
Information in this document applies to any platform.

Goal

This document describes how to survive (protect from deletion) application configuration files, which are being copied to the GlassFish environment in a Application Server (AS) cluster. Without the additional configuration steps, these files are going to be deleted whenever the AS cluster and/or NodeAgent (NA) is restarted.



Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms