The application contains seeded metadata packaged in a MAR. You should deploy your applications to MDS in the following situations, so that the metadata can be managed after deployment: A Metadata Archive (MAR), a compressed archive of selected metadata, is used to deploy metadata content to the MDS Repository, which contains the metadata for the application. Those deployed applications can be custom Java EE applications developed by your organization and some Oracle Fusion Middleware component applications, such as Oracle B2B and Oracle Web Services Manager. Oracle Metadata Services (MDS) Repository contains metadata for certain types of deployed applications. Most components, such as Oracle BPEL Process Manager, require that a schema be installed in a database, necessitating the use of a database-based repository. For production environments, you use a database-based repository. You can create a database-based repository or, for MDS, a database-based repository or a file-based repository. For information related specifically to the MDS Repository type, see Section 14.3. This includes custom Java EE applications developed by your organization and some Oracle Fusion Middleware component applications, such as Oracle B2B. A repository type represents a specific schema or set of schemas that belong to a specific Oracle Fusion Middleware component (for example, Oracle BPEL Process Manager or Oracle Internet Directory.)Ī particular type of repository, the Oracle Metadata Services (MDS) Repository, contains metadata for certain types of deployed applications. Oracle Fusion Middleware supports multiple repository types. It can also contain metadata about the configuration of Oracle Fusion Middleware and metadata for your applications. A metadata repository contains metadata for Oracle Fusion Middleware components, such as Oracle BPEL Process Manager, Oracle B2B, and Oracle WebCenter.

Java deadlock locktimout