ASAP 2.7 Extension Manual

Implementing the ASAP Extension in an Application
HP NonStop ASAP Extension Manual—425265-004
4-3
Designing Domain Names
•
All callers to all ASAPX procedures must be named. ASAPX uses the process
name of the registering process to track domain availability and to ensure
uniqueness of domain names.
•
All ASAPX API procedures return a completion code that the application processes
calling those procedures must check. If the ASAP_REGISTER_ procedure returns
an error, the registration failed. Turn off the updating of metrics until the registration
problem is corrected. The same is true for many errors returned from the other API
procedures. For more information on errors returned by the ASAPX API
procedures, see the description of the specific procedure call.
•
Applications using ASAPX must not alter shared memory without using the ASAPX
API procedures. Applications that update the shared memory segment outside of
the ASAPX API procedures can contaminate memory for all domains.
•
Any application that already allocates and uses extended memory must pass a
unique segment identifier number and segment base address to ASAPX in the
ASAP_REGISTER_ procedure call, and must supply the same value to
ASAP_REMOVE_ if deallocating the shared extended segment.
Designing Domain Names
Domain names are key elements in the ASAP architecture. They must follow domain
name rules and be carefully designed to take full advantage of ASAP. The two key
elements of a good domain name are uniqueness of the full domain name and a
balanced tree design.
To define a domain name to ASAP, include the domain name information when
registering with ASAPX. The domain name is a required parameter to the
ASAP_REGISTER_ procedure.
Domain Name Rules
•
The first part of a domain name must be the entity name as defined in EDL for your
application. If no EDL is defined, domains are registered in the generic APP entity
where no metrics are defined.
•
Names can be from 1 to 64 bytes in total length.
•
Names can contain from one to five levels separated by a backslash.
•
Unless turned off, ASAPX adds one level to each domain name by appending a
backslash and the process name of the registering process. If this behavior is
active, the supplied domain name length cannot exceed 64 bytes less the length of
the process name plus one, and cannot have more than 4 levels. The length and
level restrictions apply to the result of the ASAPX append operation.
•
Names cannot start with a backslash.
•
Names cannot contain a quote, colon, or semicolon. These are special characters
within ASAP, OEM, and Object Integration Layer (OIL).