HP CloudSystem Foundation Instrukcja Użytkownika Pobierz pdf (Strona 15)

Technical white paper | Integrated Billing Solutions with HP CSA 4.00

Save the

catalogId

value.

Next, get the ID of the <initiatingServiceRequest>. This includes information from the original request submission. Look for

the value of /ServiceSubscription/initiatingRequest/ID. An example of this would be:

<id>

90cec3a03a93ef89013a93faa4cd0040

</id>

…

<id>

<id>initiatingRequestId</id>

Now use the catalogId and initiatingRequestId with the /csa/rest/catalog call to get the desired subscriber information.

REST Syntax:

GET http://<host>:<port>/csa/rest/catalog/<catalogId>/request/

<initiatingRequestId>&userIdentifier=<subscriberId>

Response Format

…

<id>subscriberId</id>

…

<name>subscriberName</name>

<displayName>subscriberDisplayName</displayName>

…

</createdBy>

…

</ServiceRequest>

Part 8. HP CSA 4.00 Changes and Issues

• The lifecycleExecutionStatus field may or may not exist in a given record. If the requested service was based on a

Sequenced (lifecyle actions & Operations Orchestration) design, then the field will exist. If the service was based on a

Topology design, the field will not exist. You may need to update your parser to handle this condition.

• HP CSA 4.00 introduces a new method for designing services. The Topology Designer uses a “prescriptive” model for

specifying designs, and the HP CSA 4.00 Topology plug-in service works with HP Cloud OS and OpenStack to realize the

subscription request. You may wish to collect data describing which subscriptions are based on Sequenced designs, and

which are based on Topology designs. In HP CSA subscription records, this is known as an “experience type”. The syntax

to get the experience type is:

/csa/rest/catalog/%s/instance/%s?userIdentifier=%s

To make this call, you’re going to need both the catalog ID and the instance ID. The location of these fields is shown

above in Step 4. The response will be in the path /ServiceInstance/serviceDesignerExperienceType, and will be either

SEQUENCE_BASED or TOPOLOGY_BASED.

• Beware of very large XML responses. There is a defect in the initial release of HP CSA 4.00: XML responses may include

user-specified attachments and service offering attachments. These can be large text documents, diagrams, and zip

files. The HP CSA 4.01 patch removes these unwanted attachments, and XML size and performance return to normal. Be

sure to install this patch!

1 2 ... 10 11 12 13 14 15 16

Komentarze do niniejszej Instrukcji

Brak uwag

HP CloudSystem Foundation Instrukcja Użytkownika Strona 15

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Nie HP CloudSystem Foundation