Enum Class OMRSAuditCode
- All Implemented Interfaces:
Serializable
,Comparable<OMRSAuditCode>
,Constable
,AuditLogMessageSet
The OMRSAuditCode is used to define the message content for the OMRS Audit Log.
The 5 fields in the enum are:
- Log Message id: to uniquely identify the message
- Severity: is this an event, decision, action, error or exception
- Log Message Text: includes placeholder to allow additional values to be captured
- Additional Information: further parameters and data relating to the audit message (optional)
- System Action: describes the result of the situation
- User Action: describes how a user should correct the situation
-
Nested Class Summary
Nested classes/interfaces inherited from class java.lang.Enum
Enum.EnumDesc<E extends Enum<E>>
-
Enum Constant Summary
Enum ConstantDescriptionOMRS-AUDIT-0306 - A new type called {0} (guid {1}) is being maintained through the API of server {2}.OMRS-AUDIT-0036 - The connector to the local repository archive store failed with a {0} exception and the following error message: {1}OMRS-AUDIT-0037 - The connector to the local repository audit log destination failed with a {0} exception and the following error message: {1}OMRS-AUDIT-9015 - {0} has passed the {1} an invalid instance within an inbound event reportedly to be from server {2} of type {3} and owned by organization {4}.OMRS-AUDIT-0035 - The connector to the local repository event mapper failed with a {0} exception and the following error message: {1}OMRS-AUDIT-0034 - The connector to the local repository failed with a {0} exception and the following error message: {1}OMRS-AUDIT-0038 - The connector to the {0} topic failed with a {1} exception and the following error message: {2}OMRS-AUDIT-0006 - Configuration error detected while connecting to cohort {0}, exception {1} was caught with error message: {2}OMRS-AUDIT-0008 - Disconnecting from cohort {0}OMRS-AUDIT-0005 - Connecting to open metadata repository cohort {0}OMRS-AUDIT-0009 - Unregistering from cohort {0}OMRS-AUDIT-0027 - The local server is unable to initiate a connection to the cohort {0} when starting up, exception {1} was caught with error message: {2}OMRS-AUDIT-0053 - The Open Metadata Repository Services (OMRS) has processed {0} types and {1} instances from open metadata archive {2}OMRS-AUDIT-0044 - The connector for the local repository is being started in mode {0} using connector provider {1} and configuration properties {2}OMRS-AUDIT-0042 - The enterprise OMRS Connector for the {0} has shutdownOMRS-AUDIT-0033 - The {0} event manager is sending out the {1} instance events that were generated and buffered during server initializationOMRS-AUDIT-0032 - The {0} event manager is sending out the {1} type definition events that were generated and buffered during server initializationOMRS-AUDIT-0206 - Server {0} that hosts metadata collection {1} has detected that there are two different instances with the same guid of {2}: the instance from {3} has a type of {4} has a provenance type of {5} and the other instance from metadata collection {6} has a type of {7} - the instance in metadata collection {6} should have its guid changed.OMRS-AUDIT-0051 - The Open Metadata Repository Services (OMRS) is unable to process an open metadata archive because it is emptyOMRS-AUDIT-0002 - Enterprise access through the Enterprise Repository Services is initializingOMRS-AUDIT-9013 - Disconnecting of the enterprise connector manager generated an exception with message {0}OMRS-AUDIT-0043 - The start-up of an enterprise OMRS Connector for the {0} failed with exception {1} and error message: {2}OMRS-AUDIT-9012 - Disconnecting from the {0} enterprise topic connector generated a {1} exception with message {2}OMRS-AUDIT-0022 - The local repository event mapper connector {0} has no connector to an event busOMRS-AUDIT-0025 - The local repository event mapper connector {0} has disconnected the event bus connectorsOMRS-AUDIT-0023 - The local repository event mapper connector {0} has registered with an event bus connector connected to topic {1}OMRS-AUDIT-0024 - The local repository event mapper connector {0} is ready to send and receive eventsOMRS-AUDIT-0100 - Unable parse an incoming event {0} due to exception {1}OMRS-AUDIT-0101 - Unable process an incoming event {0} due to exception {1} from listener {2}OMRS-AUDIT-0130 - The enterprise repository services are managing federated queries to the following list of servers: {0}OMRS-AUDIT-0039 - Ignoring duplicate request to classify entity {0} with classification {1} in the {2} repositoryOMRS-AUDIT-0109 - Registration error occurred in cohort {0} because remote server {1} that hosts metadata collection {2} is unable to use connection {3} to create a connector to this local serverOMRS-AUDIT-0107 - Registration request for this server in cohort {0} was rejected by server {1} that hosts metadata collection {2} because the local metadata collection id {3} is not unique for this cohortOMRS-AUDIT-0108 - Two servers in cohort {0} are using the same metadata collection identifier {1}OMRS-AUDIT-0201 - Server {1} in cohort {0} that hosts metadata collection {2} has detected that TypeDef {3} ({4}) in the local server conflicts with TypeDef {5} ({6}) in the remote serverOMRS-AUDIT-0202 - Registration request for this server in cohort {0} was rejected by server {1} that hosts metadata collection {2} because TypeDef {3} ({4}) in the local server is at version {5} which is different from this TypeDef in the remote server which is at version {6}OMRS-AUDIT-0029 - The {0} event manager is initializingOMRS-AUDIT-0207 - Server {0} that hosts metadata collection {1} has changed the unique identifier (guid) of an instance of type {2} from {3} to {4}OMRS-AUDIT-0209 - Server {0} that hosts metadata collection {1} has detected that the version of the type being used by instance with the unique identifier (guid) of {2} has regressed; the type that this server is using locally is {3} and the type from the instance from metadata collection {4} is {5}; the two versions need to be reconciled.OMRS-AUDIT-8007 - An invalid instance was found in a batch of reference instances send by a remote member of the cohort.OMRS-AUDIT-0210 - Server {0} that hosts metadata collection {1} has detected that the version of the type being used by the local instance with the unique identifier (guid) of {2} has regressed; the type that the reporting server is using locally is {3} and the type from the instance from this metadata collection {4} is {5}; the two versions need to be reconciled.OMRS-AUDIT-0028 - A reference instance has been passed to the local repository on the {0} parameter of the {1} method which has the local repository metadata collection id {2} as its homeOMRS-AUDIT-0014 - Unable to disconnect processing in the local repository due to error {0}OMRS-AUDIT-0013 - Unable to start processing in the local repository due to error {0}OMRS-AUDIT-0003 - The local repository is initializing the metadata collection named {0} with an id of {1}OMRS-AUDIT-0111 - Server {0} hosting metadata collection {1} has left cohort {2}OMRS-AUDIT-0004 - Connecting to the metadata highwayOMRS-AUDIT-0118 - Unable to process the {0} request for cohort {1} from cohort member {2} because there is no cohort registry storeOMRS-AUDIT-0040 - An enterprise OMRS connector has been created for the {0}OMRS-AUDIT-8003 - Version {0} of the instance {1} from server {2} has a new metadata collection id of {3}.OMRS-AUDIT-0110 - A new registration request has been received for cohort {0} from server {1} that hosts metadata collection {2}OMRS-AUDIT-0045 - The connector for the local repository has been initializedOMRS-AUDIT-0127 - A new remote member from server {0} for cohort {1} is being configured into the enterprise connector manager.OMRS-AUDIT-0132 - A new remote connector from server {0} with metadata collection id {1} has been deployed to enterprise connector for {2}OMRS-AUDIT-0129 - A exception occurred whilst adding a new remote member from server {0} for cohort {1} into the enterprise connector manager.OMRS-AUDIT-0301 - The local server has added a new type called {0} with a unique identifier of {1} and a version number of {2} from {3}OMRS-AUDIT-0319 - The local server does not have a local repository and so a new type called {0} with a unique identifier of {1} and a version number of {2} from {3} is just cached for informationOMRS-AUDIT-8004 - Version {0} of the instance {1} from server {2} and metadata collection {3} has a new type of {4} ({5}).OMRS-AUDIT-0302 - The local server is unable to add a new type called {0} with a unique identifier of {1} and a version number of {2} because the server does not support this featureOMRS-AUDIT-0055 - The Open Metadata Repository Services (OMRS) is not processing instances from the archive because it does not have a local repositoryOMRS-AUDIT-0012 - No events will be sent to the open metadata repository cohort {0} because the local metadata collection id is nullOMRS-AUDIT-0054 - The Open Metadata Repository Services (OMRS) is not processing type definitions from the archive because it does not have a type processorOMRS-AUDIT-0102 - Connector {0} is unable to process a null event {0} passed by the event busOMRS-AUDIT-0317 - The local server method {0} has been asked to process a request from {1} containing a null instanceOMRS-AUDIT-0315 - The local server has been asked to process a request from {0} containing a containing an instance with type {1} ({2}) of category {3} but a null unique identifier (GUID)OMRS-AUDIT-9008 - Unable to send or receive a metadata instance event because the event processor is nullOMRS-AUDIT-0316 - The local server method {0} has been asked to process a request from {1} containing an instance with unique identifier {2} and type {3} ({4}) of category {5} but a null unique home metadata collection identifier (GUID)OMRS-AUDIT-9009 - Unable to initialize part of the Open Metadata Repository Service (OMRS) because the configuration is nullOMRS-AUDIT-9002 - Unable to process a received event from topic {0} because its content is nullOMRS-AUDIT-0052 - The Open Metadata Repository Services (OMRS) is unable to process an open metadata archive {0} because it has no control headerOMRS-AUDIT-0126 - A null member record has been stored in the cohort registry storeOMRS-AUDIT-9006 - Unable to send or receive a registry event because the event processor is nullOMRS-AUDIT-0017 - Unable to send or receive events for cohort {0} because the connector to the OMRS Topic failed to initializeOMRS-AUDIT-0313 - The local server method {0} has been asked to process a request from {1} that contains a null typeOMRS-AUDIT-0311 - The local server has been asked to process a request from {0} containing a type {1} ({2}) with a null type categoryOMRS-AUDIT-0308 - The local server has detected a type called {0} from {1} with a null unique identifierOMRS-AUDIT-0309 - The local server has detected a type from {0} with a null unique name.OMRS-AUDIT-9007 - Unable to send or receive a TypeDef event because the event processor is nullOMRS-AUDIT-0064 - The Open Metadata Repository Services (OMRS) has initialized the audit log for the {0} called {1}OMRS-AUDIT-0011 - The Open Metadata Repository Services (OMRS) has disconnected from the open metadata repositoriesOMRS-AUDIT-0010 - The Open Metadata Repository Services (OMRS) is disconnecting the open metadata repositoriesOMRS-AUDIT-0007 - The Open Metadata Repository Services (OMRS) has initializedOMRS-AUDIT-0001 - The Open Metadata Repository Services (OMRS) is initializing the subsystems to support a new serverOMRS-AUDIT-0026 - Initializing listener for cohort {0}OMRS-AUDIT-0018 - The OMRS Topic Listener has no embedded connector to an event busOMRS-AUDIT-0021 - The OMRS Topic Listener has disconnected the event bus connectors for topic {0}OMRS-AUDIT-0019 - An OMRS Topic Connector has registered with an event bus connector for topic {0}OMRS-AUDIT-0020 - An OMRS Topic Connector is ready to send and receive events on topic {0}OMRS-AUDIT-0016 - The listener thread for the OMRS Topic Connector for topic {0} has shutdownOMRS-AUDIT-0015 - The listener thread for an OMRS Topic Connector for topic {0} has startedOMRS-AUDIT-8009 - The Open Metadata Repository Services (OMRS) has sent event of type {0} to the cohort topic {1}OMRS-AUDIT-0114 - Registration error occurred in cohort {0} because the local server is not able to use the remote connection {1} supplied by server {2} that hosts metadata collection {3} to create a connector to its metadata repository.OMRS-AUDIT-0113 - Registration request received from cohort {0} was rejected by the local server because the remote server {1} is using a metadata collection id {2} that is not unique in the cohortOMRS-AUDIT-0203 - The local server has detected a conflict in cohort {0} in the registration request from server {1} that hosts metadata collection {2}.OMRS-AUDIT-0205 - The local server in cohort {0} has rejected a TypeDef update from server {1} that hosts metadata collection {2} because the version of TypeDef {3} ({4}) in the local server is at version {5} is different to this TypeDef in the remote server which is at version {6}OMRS-AUDIT-0204 - The local server in cohort {0} has rejected a TypeDef update from server {1} that hosts metadata collection {2} because the version of TypeDef {3} ({4}) in the local server is at version {5} is different from this TypeDef in the remote server which is at version {6}OMRS-AUDIT-8006 - Processing incoming event of type {0} for instance {1} from: {2}OMRS-AUDIT-8005 - An instance of type {0} ({1}) from server {2} and metadata collection {3} is using the same guid {4} as a stored instance of type {5} ({6})OMRS-AUDIT-8002 - A later version of the instance {0} from server {1} and metadata collection {2} is using an older version of the type {3}.OMRS-AUDIT-8001 - Received unknown event: {0}OMRS-AUDIT-0050 - The Open Metadata Repository Services (OMRS) is about to process open metadata archive {0}OMRS-AUDIT-0061 - Refreshing local registration information with open metadata repository cohort {0} using metadata collection id {1}OMRS-AUDIT-0062 - Requesting registration information from other members of the open metadata repository cohort {0}OMRS-AUDIT-0112 - A re-registration request has been received for cohort {0} from server {1} that hosts metadata collection {2}OMRS-AUDIT-0106 - Refreshing registration with open metadata repository cohort {0} using metadata collection id {1} at the request of server {2}OMRS-AUDIT-0060 - Registering with open metadata repository cohort {0} using metadata collection id {1}OMRS-AUDIT-0030 - Registering the {0} event consumer with the {1} event managerOMRS-AUDIT-0133 - Information about remote connector from server {0} with metadata collection id {1} has been refreshed in enterprise connector for {2}OMRS-AUDIT-0128 - Configuration received for an existing remote member from server {0} for cohort {1} has not changed.OMRS-AUDIT-0134 - The remote connector for metadata collection id {0} is no longer being called by {1}OMRS-AUDIT-0135 - Configuration for an existing remote member from server {0} for cohort {1} has changed and is being updated in the enterprise connector manager.OMRS-AUDIT-0307 - Conflicting type definitions for type {0} ({1}) have been detected in remote system {2} ({3}).OMRS-AUDIT-0131 - A remote member from cohort {0} with metadata collection id {1} is being removed by the enterprise connector managerOMRS-AUDIT-8008 - Retrying retrieve of an entity {0} for user {1} because only a proxy is available - attempt {2}OMRS-AUDIT-9005 - Unable to send or receive a metadata instance event for cohort {0} due to an error in the OMRS Topic ConnectorOMRS-AUDIT-0105 - Unable to send a registry event for cohort {0} due to an error in the OMRS Topic ConnectorOMRS-AUDIT-9003 - Unable to send a TypeDef event for cohort {0} due to an error in the OMRS Topic ConnectorOMRS-AUDIT-9010 - Unable to send an event because the event is of an unknown typeOMRS-AUDIT-0401 - Skipping call to repository {0} since it is not responding correctly.OMRS-AUDIT-0047 - The connector for the local repository has been startedOMRS-AUDIT-0041 - The enterprise OMRS connector for the {0} has startedOMRS-AUDIT-0031 - The {0} event manager is starting with {1} type definition event consumer(s) and {2} instance event consumer(s)OMRS-AUDIT-0046 - The connector for the local repository is about to be startedOMRS-AUDIT-0318 - The local server has recognized a new type called {0} with a unique identifier of {1} and a version number of {2} from {3}OMRS-AUDIT-0305 - The local server has detected a conflict with an existing type called {0} with a unique identifier of {1}.OMRS-AUDIT-0304 - The local server has removed an existing type called {0} with a unique identifier of {1}; requester is {2}OMRS-AUDIT-0320 - A patch to the {0} ({1}) type definition was ignored because it is to be applied to the {2} version of the type and the patch is for version {3}OMRS-AUDIT-0303 - The local server has updated an existing type called {0} with a unique identifier of {1} to version number of {2} using a patch from {3}OMRS-AUDIT-0314 - The local server has been asked to process a request from {0} containing a containing an instance with type {1} ({2}) of category {3} but a version of {4}.OMRS-AUDIT-0208 - Server {0} that hosts metadata collection {1} was unable to change the unique identifier (guid) of an instance of type {2} from {3}.OMRS-AUDIT-0211 - Server {0} that hosts metadata collection {1} was unable to remove the reference copy of an instance of type {2} with unique identifier (guid) of {3}.OMRS-AUDIT-9014 - The Open Metadata Repository Service has generated an unexpected {0} exception during method {1}.OMRS-AUDIT-9011 - An incoming event of type {0} from {1} ({2}) generated an exception of type {3} with message {4}OMRS-AUDIT-0136 - A {0} exception was received from a remote repository with metadata collection id {1} during {2}.OMRS-AUDIT-9016 - The topic listener for the {0} service caught an unexpected exception {1} with message {2}OMRS-AUDIT-9018 - Exception {0} occurred when processing a type {1} from {2}.OMRS-AUDIT-9017 - The topic listener for the {0} service threw an unexpected exception {1} with message {2}OMRS-AUDIT-9019 - The type definition event processor for the {0} service caught an unexpected exception {1} with message {2}OMRS-AUDIT-0310 - The local server has been asked to process a request from {0} containing an unrecognized type {1} ({2})OMRS-AUDIT-0312 - The local server has been asked to process a request from {0} containing a type {1} ({2}) with an unexpected type category of {3}.OMRS-AUDIT-0321 - A patch to the {0} ({1}) type definition from {2} was ignored because the local repository does not support this typeOMRS-AUDIT-0063 - Unregistering with open metadata repository cohort {0} using metadata collection id {1}OMRS-AUDIT-0137 - The remote repository {0} with metadata collection id {1} does not support method {2}OMRS-AUDIT-0322 - The local server does not have a local repository and so an update to the type called {0} with a unique identifier of {1} that applies to version number of {2} from {3} is just cached for information -
Method Summary
Modifier and TypeMethodDescriptionRetrieve a message definition object for logging.getMessageDefinition
(String... params) Retrieve a message definition object for logging.toString()
JSON-style toStringstatic OMRSAuditCode
Returns the enum constant of this class with the specified name.static OMRSAuditCode[]
values()
Returns an array containing the constants of this enum class, in the order they are declared.
-
Enum Constant Details
-
OMRS_INITIALIZING
OMRS-AUDIT-0001 - The Open Metadata Repository Services (OMRS) is initializing the subsystems to support a new server -
ENTERPRISE_ACCESS_INITIALIZING
OMRS-AUDIT-0002 - Enterprise access through the Enterprise Repository Services is initializing -
LOCAL_REPOSITORY_INITIALIZING
OMRS-AUDIT-0003 - The local repository is initializing the metadata collection named {0} with an id of {1} -
METADATA_HIGHWAY_INITIALIZING
OMRS-AUDIT-0004 - Connecting to the metadata highway -
COHORT_INITIALIZING
OMRS-AUDIT-0005 - Connecting to open metadata repository cohort {0} -
COHORT_CONFIG_ERROR
OMRS-AUDIT-0006 - Configuration error detected while connecting to cohort {0}, exception {1} was caught with error message: {2} -
OMRS_INITIALIZED
OMRS-AUDIT-0007 - The Open Metadata Repository Services (OMRS) has initialized -
COHORT_DISCONNECTING
OMRS-AUDIT-0008 - Disconnecting from cohort {0} -
COHORT_PERMANENTLY_DISCONNECTING
OMRS-AUDIT-0009 - Unregistering from cohort {0} -
OMRS_DISCONNECTING
OMRS-AUDIT-0010 - The Open Metadata Repository Services (OMRS) is disconnecting the open metadata repositories -
OMRS_DISCONNECTED
OMRS-AUDIT-0011 - The Open Metadata Repository Services (OMRS) has disconnected from the open metadata repositories -
NO_LOCAL_REPOSITORY
OMRS-AUDIT-0012 - No events will be sent to the open metadata repository cohort {0} because the local metadata collection id is null -
LOCAL_REPOSITORY_FAILED_TO_START
OMRS-AUDIT-0013 - Unable to start processing in the local repository due to error {0} -
LOCAL_REPOSITORY_FAILED_TO_DISCONNECT
OMRS-AUDIT-0014 - Unable to disconnect processing in the local repository due to error {0} -
OPEN_METADATA_TOPIC_LISTENER_START
OMRS-AUDIT-0015 - The listener thread for an OMRS Topic Connector for topic {0} has started -
OPEN_METADATA_TOPIC_LISTENER_SHUTDOWN
OMRS-AUDIT-0016 - The listener thread for the OMRS Topic Connector for topic {0} has shutdown -
NULL_TOPIC_CONNECTOR
OMRS-AUDIT-0017 - Unable to send or receive events for cohort {0} because the connector to the OMRS Topic failed to initialize -
OMRS_TOPIC_LISTENER_DEAF
OMRS-AUDIT-0018 - The OMRS Topic Listener has no embedded connector to an event bus -
OMRS_TOPIC_LISTENER_REGISTERED
OMRS-AUDIT-0019 - An OMRS Topic Connector has registered with an event bus connector for topic {0} -
OMRS_TOPIC_LISTENER_STARTED
OMRS-AUDIT-0020 - An OMRS Topic Connector is ready to send and receive events on topic {0} -
OMRS_TOPIC_LISTENER_DISCONNECTED
OMRS-AUDIT-0021 - The OMRS Topic Listener has disconnected the event bus connectors for topic {0} -
EVENT_MAPPER_LISTENER_DEAF
OMRS-AUDIT-0022 - The local repository event mapper connector {0} has no connector to an event bus -
EVENT_MAPPER_LISTENER_REGISTERED
OMRS-AUDIT-0023 - The local repository event mapper connector {0} has registered with an event bus connector connected to topic {1} -
EVENT_MAPPER_LISTENER_STARTED
OMRS-AUDIT-0024 - The local repository event mapper connector {0} is ready to send and receive events -
EVENT_MAPPER_LISTENER_DISCONNECTED
OMRS-AUDIT-0025 - The local repository event mapper connector {0} has disconnected the event bus connectors -
OMRS_LISTENER_INITIALIZING
OMRS-AUDIT-0026 - Initializing listener for cohort {0} -
COHORT_STARTUP_ERROR
OMRS-AUDIT-0027 - The local server is unable to initiate a connection to the cohort {0} when starting up, exception {1} was caught with error message: {2} -
LOCAL_REFERENCE_INSTANCE
OMRS-AUDIT-0028 - A reference instance has been passed to the local repository on the {0} parameter of the {1} method which has the local repository metadata collection id {2} as its home -
INITIALIZING_EVENT_MANAGER
OMRS-AUDIT-0029 - The {0} event manager is initializing -
REGISTERING_EVENT_PROCESSOR
OMRS-AUDIT-0030 - Registering the {0} event consumer with the {1} event manager -
STARTING_EVENT_MANAGER
OMRS-AUDIT-0031 - The {0} event manager is starting with {1} type definition event consumer(s) and {2} instance event consumer(s) -
DRAINING_TYPEDEF_EVENT_BUFFER
OMRS-AUDIT-0032 - The {0} event manager is sending out the {1} type definition events that were generated and buffered during server initialization -
DRAINING_INSTANCE_EVENT_BUFFER
OMRS-AUDIT-0033 - The {0} event manager is sending out the {1} instance events that were generated and buffered during server initialization -
BAD_REAL_LOCAL_REPOSITORY_CONNECTOR
OMRS-AUDIT-0034 - The connector to the local repository failed with a {0} exception and the following error message: {1} -
BAD_REAL_LOCAL_EVENT_MAPPER
OMRS-AUDIT-0035 - The connector to the local repository event mapper failed with a {0} exception and the following error message: {1} -
BAD_ARCHIVE_STORE
OMRS-AUDIT-0036 - The connector to the local repository archive store failed with a {0} exception and the following error message: {1} -
BAD_AUDIT_LOG_DESTINATION
OMRS-AUDIT-0037 - The connector to the local repository audit log destination failed with a {0} exception and the following error message: {1} -
BAD_TOPIC_CONNECTION
OMRS-AUDIT-0038 - The connector to the {0} topic failed with a {1} exception and the following error message: {2} -
IGNORING_DUPLICATE_CLASSIFICATION
OMRS-AUDIT-0039 - Ignoring duplicate request to classify entity {0} with classification {1} in the {2} repository -
NEW_ENTERPRISE_CONNECTOR
OMRS-AUDIT-0040 - An enterprise OMRS connector has been created for the {0} -
STARTING_ENTERPRISE_CONNECTOR
OMRS-AUDIT-0041 - The enterprise OMRS connector for the {0} has started -
DISCONNECTING_ENTERPRISE_CONNECTOR
OMRS-AUDIT-0042 - The enterprise OMRS Connector for the {0} has shutdown -
ENTERPRISE_CONNECTOR_FAILED
OMRS-AUDIT-0043 - The start-up of an enterprise OMRS Connector for the {0} failed with exception {1} and error message: {2} -
CREATING_REAL_CONNECTOR
OMRS-AUDIT-0044 - The connector for the local repository is being started in mode {0} using connector provider {1} and configuration properties {2} -
NEW_REAL_CONNECTOR
OMRS-AUDIT-0045 - The connector for the local repository has been initialized -
STARTING_REAL_CONNECTOR
OMRS-AUDIT-0046 - The connector for the local repository is about to be started -
STARTED_REAL_CONNECTOR
OMRS-AUDIT-0047 - The connector for the local repository has been started -
PROCESSING_ARCHIVE
OMRS-AUDIT-0050 - The Open Metadata Repository Services (OMRS) is about to process open metadata archive {0} -
EMPTY_ARCHIVE
OMRS-AUDIT-0051 - The Open Metadata Repository Services (OMRS) is unable to process an open metadata archive because it is empty -
NULL_PROPERTIES_IN_ARCHIVE
OMRS-AUDIT-0052 - The Open Metadata Repository Services (OMRS) is unable to process an open metadata archive {0} because it has no control header -
COMPLETED_ARCHIVE
OMRS-AUDIT-0053 - The Open Metadata Repository Services (OMRS) has processed {0} types and {1} instances from open metadata archive {2} -
NO_TYPE_DEF_PROCESSOR
OMRS-AUDIT-0054 - The Open Metadata Repository Services (OMRS) is not processing type definitions from the archive because it does not have a type processor -
NO_INSTANCE_PROCESSOR
OMRS-AUDIT-0055 - The Open Metadata Repository Services (OMRS) is not processing instances from the archive because it does not have a local repository -
REGISTERED_WITH_COHORT
OMRS-AUDIT-0060 - Registering with open metadata repository cohort {0} using metadata collection id {1} -
RE_REGISTERED_WITH_COHORT
OMRS-AUDIT-0061 - Refreshing local registration information with open metadata repository cohort {0} using metadata collection id {1} -
REFRESH_REGISTRATION_REQUEST_WITH_COHORT
OMRS-AUDIT-0062 - Requesting registration information from other members of the open metadata repository cohort {0} -
UNREGISTERING_FROM_COHORT
OMRS-AUDIT-0063 - Unregistering with open metadata repository cohort {0} using metadata collection id {1} -
OMRS_AUDIT_LOG_READY
OMRS-AUDIT-0064 - The Open Metadata Repository Services (OMRS) has initialized the audit log for the {0} called {1} -
EVENT_PARSING_ERROR
OMRS-AUDIT-0100 - Unable parse an incoming event {0} due to exception {1} -
EVENT_PROCESSING_ERROR
OMRS-AUDIT-0101 - Unable process an incoming event {0} due to exception {1} from listener {2} -
NULL_EVENT_TO_PROCESS
OMRS-AUDIT-0102 - Connector {0} is unable to process a null event {0} passed by the event bus -
SEND_REGISTRY_EVENT_ERROR
OMRS-AUDIT-0105 - Unable to send a registry event for cohort {0} due to an error in the OMRS Topic Connector -
REFRESHING_REGISTRATION_WITH_COHORT
OMRS-AUDIT-0106 - Refreshing registration with open metadata repository cohort {0} using metadata collection id {1} at the request of server {2} -
INCOMING_CONFLICTING_LOCAL_METADATA_COLLECTION_ID
OMRS-AUDIT-0107 - Registration request for this server in cohort {0} was rejected by server {1} that hosts metadata collection {2} because the local metadata collection id {3} is not unique for this cohort -
INCOMING_CONFLICTING_METADATA_COLLECTION_ID
OMRS-AUDIT-0108 - Two servers in cohort {0} are using the same metadata collection identifier {1} -
INCOMING_BAD_CONNECTION
OMRS-AUDIT-0109 - Registration error occurred in cohort {0} because remote server {1} that hosts metadata collection {2} is unable to use connection {3} to create a connector to this local server -
NEW_MEMBER_IN_COHORT
OMRS-AUDIT-0110 - A new registration request has been received for cohort {0} from server {1} that hosts metadata collection {2} -
MEMBER_LEFT_COHORT
OMRS-AUDIT-0111 - Server {0} hosting metadata collection {1} has left cohort {2} -
REFRESHED_MEMBER_IN_COHORT
OMRS-AUDIT-0112 - A re-registration request has been received for cohort {0} from server {1} that hosts metadata collection {2} -
OUTGOING_CONFLICTING_METADATA_COLLECTION_ID
OMRS-AUDIT-0113 - Registration request received from cohort {0} was rejected by the local server because the remote server {1} is using a metadata collection id {2} that is not unique in the cohort -
OUTGOING_BAD_CONNECTION
OMRS-AUDIT-0114 - Registration error occurred in cohort {0} because the local server is not able to use the remote connection {1} supplied by server {2} that hosts metadata collection {3} to create a connector to its metadata repository. Error message is {4} -
MISSING_MEMBER_REGISTRATION
OMRS-AUDIT-0118 - Unable to process the {0} request for cohort {1} from cohort member {2} because there is no cohort registry store -
NULL_REGISTERED_MEMBER
OMRS-AUDIT-0126 - A null member record has been stored in the cohort registry store -
NEW_REMOTE_MEMBER
OMRS-AUDIT-0127 - A new remote member from server {0} for cohort {1} is being configured into the enterprise connector manager. It has a metadata collection id of {2}, a metadata collection name of {3}, the server type is {4} and its owning organization is {5} -
REMOTE_MEMBER_REFRESHED
OMRS-AUDIT-0128 - Configuration received for an existing remote member from server {0} for cohort {1} has not changed. It has a metadata collection id of {2}, a metadata collection name of {3}, the server type is {4} and its owning organization is {5} -
NEW_REMOTE_MEMBER_FAILURE
OMRS-AUDIT-0129 - A exception occurred whilst adding a new remote member from server {0} for cohort {1} into the enterprise connector manager. The exception was {2} and the error message was {3} -
FEDERATION_LIST
OMRS-AUDIT-0130 - The enterprise repository services are managing federated queries to the following list of servers: {0} -
REMOVE_REMOTE_MEMBER
OMRS-AUDIT-0131 - A remote member from cohort {0} with metadata collection id {1} is being removed by the enterprise connector manager -
NEW_REMOTE_MEMBER_DEPLOYED
OMRS-AUDIT-0132 - A new remote connector from server {0} with metadata collection id {1} has been deployed to enterprise connector for {2} -
REMOTE_MEMBER_DEPLOY_REFRESH
OMRS-AUDIT-0133 - Information about remote connector from server {0} with metadata collection id {1} has been refreshed in enterprise connector for {2} -
REMOTE_MEMBER_UNDEPLOYED
OMRS-AUDIT-0134 - The remote connector for metadata collection id {0} is no longer being called by {1} -
REMOTE_MEMBER_UPDATED
OMRS-AUDIT-0135 - Configuration for an existing remote member from server {0} for cohort {1} has changed and is being updated in the enterprise connector manager. It has a metadata collection id of {2}, a metadata collection name of {3}, the server type is {4} and its owning organization is {5} -
UNEXPECTED_EXCEPTION_FROM_REPOSITORY
OMRS-AUDIT-0136 - A {0} exception was received from a remote repository with metadata collection id {1} during {2}. The exception message was {3} -
UNSUPPORTED_REMOTE_FUNCTION
OMRS-AUDIT-0137 - The remote repository {0} with metadata collection id {1} does not support method {2} -
INCOMING_CONFLICTING_TYPEDEFS
OMRS-AUDIT-0201 - Server {1} in cohort {0} that hosts metadata collection {2} has detected that TypeDef {3} ({4}) in the local server conflicts with TypeDef {5} ({6}) in the remote server -
INCOMING_TYPEDEF_PATCH_MISMATCH
OMRS-AUDIT-0202 - Registration request for this server in cohort {0} was rejected by server {1} that hosts metadata collection {2} because TypeDef {3} ({4}) in the local server is at version {5} which is different from this TypeDef in the remote server which is at version {6} -
OUTGOING_CONFLICTING_TYPEDEFS
OMRS-AUDIT-0203 - The local server has detected a conflict in cohort {0} in the registration request from server {1} that hosts metadata collection {2}. TypeDef {3} ({4}) in the local server conflicts with TypeDef {5} ({6}) in the remote server -
OUTGOING_TYPEDEF_PATCH_MISMATCH
OMRS-AUDIT-0204 - The local server in cohort {0} has rejected a TypeDef update from server {1} that hosts metadata collection {2} because the version of TypeDef {3} ({4}) in the local server is at version {5} is different from this TypeDef in the remote server which is at version {6} -
OUTGOING_TYPE_MISMATCH
OMRS-AUDIT-0205 - The local server in cohort {0} has rejected a TypeDef update from server {1} that hosts metadata collection {2} because the version of TypeDef {3} ({4}) in the local server is at version {5} is different to this TypeDef in the remote server which is at version {6} -
DUPLICATE_INSTANCES_FOR_GUID
OMRS-AUDIT-0206 - Server {0} that hosts metadata collection {1} has detected that there are two different instances with the same guid of {2}: the instance from {3} has a type of {4} has a provenance type of {5} and the other instance from metadata collection {6} has a type of {7} - the instance in metadata collection {6} should have its guid changed. The accompanying error message is : {8} -
INSTANCE_SUCCESSFULLY_REIDENTIFIED
OMRS-AUDIT-0207 - Server {0} that hosts metadata collection {1} has changed the unique identifier (guid) of an instance of type {2} from {3} to {4} -
UNABLE_TO_RE_IDENTIFY_INSTANCE
OMRS-AUDIT-0208 - Server {0} that hosts metadata collection {1} was unable to change the unique identifier (guid) of an instance of type {2} from {3}. The exception was {4} with error message {5} -
INSTANCES_WITH_CONFLICTING_TYPES
OMRS-AUDIT-0209 - Server {0} that hosts metadata collection {1} has detected that the version of the type being used by instance with the unique identifier (guid) of {2} has regressed; the type that this server is using locally is {3} and the type from the instance from metadata collection {4} is {5}; the two versions need to be reconciled. The accompanying error message is: {6} -
LOCAL_INSTANCE_WITH_CONFLICTING_TYPES
OMRS-AUDIT-0210 - Server {0} that hosts metadata collection {1} has detected that the version of the type being used by the local instance with the unique identifier (guid) of {2} has regressed; the type that the reporting server is using locally is {3} and the type from the instance from this metadata collection {4} is {5}; the two versions need to be reconciled. The accompanying error message is: {6} -
UNABLE_TO_REMOVE_REFERENCE_COPY
OMRS-AUDIT-0211 - Server {0} that hosts metadata collection {1} was unable to remove the reference copy of an instance of type {2} with unique identifier (guid) of {3}. The exception was {4} with error message: {5} -
NEW_TYPE_ADDED
OMRS-AUDIT-0301 - The local server has added a new type called {0} with a unique identifier of {1} and a version number of {2} from {3} -
NEW_TYPE_NOT_SUPPORTED
OMRS-AUDIT-0302 - The local server is unable to add a new type called {0} with a unique identifier of {1} and a version number of {2} because the server does not support this feature -
TYPE_UPDATED
OMRS-AUDIT-0303 - The local server has updated an existing type called {0} with a unique identifier of {1} to version number of {2} using a patch from {3} -
TYPE_REMOVED
OMRS-AUDIT-0304 - The local server has removed an existing type called {0} with a unique identifier of {1}; requester is {2} -
TYPE_IDENTIFIER_MISMATCH
OMRS-AUDIT-0305 - The local server has detected a conflict with an existing type called {0} with a unique identifier of {1}. This does not match the type name {2} and unique identifier {3} passed to it on a request from {4} -
AD_HOC_TYPE_DEFINITION
OMRS-AUDIT-0306 - A new type called {0} (guid {1}) is being maintained through the API of server {2}. The method called by user {3} was {4} -
REMOTE_TYPE_CONFLICT
OMRS-AUDIT-0307 - Conflicting type definitions for type {0} ({1}) have been detected in remote system {2} ({3}). Other system involved has metadata collection {4} Error message is: {5} -
NULL_TYPE_IDENTIFIER
OMRS-AUDIT-0308 - The local server has detected a type called {0} from {1} with a null unique identifier -
NULL_TYPE_NAME
OMRS-AUDIT-0309 - The local server has detected a type from {0} with a null unique name. The supplied unique identifier for the type is {1} -
UNKNOWN_TYPE
OMRS-AUDIT-0310 - The local server has been asked to process a request from {0} containing an unrecognized type {1} ({2}) -
NULL_TYPE_CATEGORY
OMRS-AUDIT-0311 - The local server has been asked to process a request from {0} containing a type {1} ({2}) with a null type category -
UNKNOWN_TYPE_CATEGORY
OMRS-AUDIT-0312 - The local server has been asked to process a request from {0} containing a type {1} ({2}) with an unexpected type category of {3}. The local type definition has a category of {4} -
NULL_TYPE
OMRS-AUDIT-0313 - The local server method {0} has been asked to process a request from {1} that contains a null type -
TYPE_VERSION_MISMATCH
OMRS-AUDIT-0314 - The local server has been asked to process a request from {0} containing a containing an instance with type {1} ({2}) of category {3} but a version of {4}. The locally supported version is {5} -
NULL_INSTANCE_ID
OMRS-AUDIT-0315 - The local server has been asked to process a request from {0} containing a containing an instance with type {1} ({2}) of category {3} but a null unique identifier (GUID) -
NULL_METADATA_COLLECTION_ID
OMRS-AUDIT-0316 - The local server method {0} has been asked to process a request from {1} containing an instance with unique identifier {2} and type {3} ({4}) of category {5} but a null unique home metadata collection identifier (GUID) -
NULL_INSTANCE
OMRS-AUDIT-0317 - The local server method {0} has been asked to process a request from {1} containing a null instance -
TYPE_ALREADY_KNOWN
OMRS-AUDIT-0318 - The local server has recognized a new type called {0} with a unique identifier of {1} and a version number of {2} from {3} -
NEW_TYPE_CACHED_FOR_ENTERPRISE
OMRS-AUDIT-0319 - The local server does not have a local repository and so a new type called {0} with a unique identifier of {1} and a version number of {2} from {3} is just cached for information -
TYPE_UPDATE_SKIPPED
OMRS-AUDIT-0320 - A patch to the {0} ({1}) type definition was ignored because it is to be applied to the {2} version of the type and the patch is for version {3} -
UNKNOWN_TYPE_UPDATE_SKIPPED
OMRS-AUDIT-0321 - A patch to the {0} ({1}) type definition from {2} was ignored because the local repository does not support this type -
UPDATED_TYPE_CACHED_FOR_ENTERPRISE
OMRS-AUDIT-0322 - The local server does not have a local repository and so an update to the type called {0} with a unique identifier of {1} that applies to version number of {2} from {3} is just cached for information -
SKIPPING_METADATA_COLLECTION
OMRS-AUDIT-0401 - Skipping call to repository {0} since it is not responding correctly. Error received was {1} with message {2} -
PROCESS_UNKNOWN_EVENT
OMRS-AUDIT-8001 - Received unknown event: {0} -
PROCESS_INSTANCE_TYPE_CONFLICT
OMRS-AUDIT-8002 - A later version of the instance {0} from server {1} and metadata collection {2} is using an older version of the type {3}. Previous type header was {4}, new type header is {5} -
NEW_HOME_INFORMATION
OMRS-AUDIT-8003 - Version {0} of the instance {1} from server {2} has a new metadata collection id of {3}. Its original metadata collection id was {4} -
NEW_TYPE_INFORMATION
OMRS-AUDIT-8004 - Version {0} of the instance {1} from server {2} and metadata collection {3} has a new type of {4} ({5}). Previous type was {6} ({7}) -
PROCESS_INSTANCE_GUID_CONFLICT
OMRS-AUDIT-8005 - An instance of type {0} ({1}) from server {2} and metadata collection {3} is using the same guid {4} as a stored instance of type {5} ({6}) -
PROCESS_INCOMING_EVENT
OMRS-AUDIT-8006 - Processing incoming event of type {0} for instance {1} from: {2} -
INVALID_INSTANCES
OMRS-AUDIT-8007 - An invalid instance was found in a batch of reference instances send by a remote member of the cohort. The exception was {0} with message {1} -
RETRY_FOR_PROXY
OMRS-AUDIT-8008 - Retrying retrieve of an entity {0} for user {1} because only a proxy is available - attempt {2} -
OUTBOUND_TOPIC_EVENT
OMRS-AUDIT-8009 - The Open Metadata Repository Services (OMRS) has sent event of type {0} to the cohort topic {1} -
NULL_OMRS_EVENT_RECEIVED
OMRS-AUDIT-9002 - Unable to process a received event from topic {0} because its content is null -
SEND_TYPEDEF_EVENT_ERROR
OMRS-AUDIT-9003 - Unable to send a TypeDef event for cohort {0} due to an error in the OMRS Topic Connector -
SEND_INSTANCE_EVENT_ERROR
OMRS-AUDIT-9005 - Unable to send or receive a metadata instance event for cohort {0} due to an error in the OMRS Topic Connector -
NULL_REGISTRY_PROCESSOR
OMRS-AUDIT-9006 - Unable to send or receive a registry event because the event processor is null -
NULL_TYPEDEF_PROCESSOR
OMRS-AUDIT-9007 - Unable to send or receive a TypeDef event because the event processor is null -
NULL_INSTANCE_PROCESSOR
OMRS-AUDIT-9008 - Unable to send or receive a metadata instance event because the event processor is null -
NULL_OMRS_CONFIG
OMRS-AUDIT-9009 - Unable to initialize part of the Open Metadata Repository Service (OMRS) because the configuration is null -
SENT_UNKNOWN_EVENT
OMRS-AUDIT-9010 - Unable to send an event because the event is of an unknown type -
UNEXPECTED_EXCEPTION_FROM_EVENT
OMRS-AUDIT-9011 - An incoming event of type {0} from {1} ({2}) generated an exception of type {3} with message {4} -
ENTERPRISE_TOPIC_DISCONNECT_ERROR
OMRS-AUDIT-9012 - Disconnecting from the {0} enterprise topic connector generated a {1} exception with message {2} -
ENTERPRISE_CONNECTOR_DISCONNECT_ERROR
OMRS-AUDIT-9013 - Disconnecting of the enterprise connector manager generated an exception with message {0} -
UNEXPECTED_EXCEPTION
OMRS-AUDIT-9014 - The Open Metadata Repository Service has generated an unexpected {0} exception during method {1}. The message was {2} -
BAD_EVENT_INSTANCE
OMRS-AUDIT-9015 - {0} has passed the {1} an invalid instance within an inbound event reportedly to be from server {2} of type {3} and owned by organization {4}. The instance is from metadata collection {5} and is of this format: {6} -
UNEXPECTED_EXCEPTION_FROM_SERVICE_LISTENER
OMRS-AUDIT-9016 - The topic listener for the {0} service caught an unexpected exception {1} with message {2} -
UNHANDLED_EXCEPTION_FROM_SERVICE_LISTENER
OMRS-AUDIT-9017 - The topic listener for the {0} service threw an unexpected exception {1} with message {2} -
UNEXPECTED_EXCEPTION_FROM_TYPE_PROCESSING
OMRS-AUDIT-9018 - Exception {0} occurred when processing a type {1} from {2}. The originator of the type was {3} ({4}). The message in the exception was {5} -
UNHANDLED_EXCEPTION_FROM_TYPE_PROCESSING
OMRS-AUDIT-9019 - The type definition event processor for the {0} service caught an unexpected exception {1} with message {2}
-
-
Method Details
-
values
Returns an array containing the constants of this enum class, in the order they are declared.- Returns:
- an array containing the constants of this enum class, in the order they are declared
-
valueOf
Returns the enum constant of this class with the specified name. The string must match exactly an identifier used to declare an enum constant in this class. (Extraneous whitespace characters are not permitted.)- Parameters:
name
- the name of the enum constant to be returned.- Returns:
- the enum constant with the specified name
- Throws:
IllegalArgumentException
- if this enum class has no constant with the specified nameNullPointerException
- if the argument is null
-
getMessageDefinition
Retrieve a message definition object for logging. This method is used when there are no message inserts.- Specified by:
getMessageDefinition
in interfaceAuditLogMessageSet
- Returns:
- message definition object.
-
getMessageDefinition
Retrieve a message definition object for logging. This method is used when there are values to be inserted into the message.- Specified by:
getMessageDefinition
in interfaceAuditLogMessageSet
- Parameters:
params
- array of parameters (all strings). They are inserted into the message according to the numbering in the message text.- Returns:
- message definition object.
-
toString
JSON-style toString- Overrides:
toString
in classEnum<OMRSAuditCode>
- Returns:
- string of property names and values for this enum
-