This class is used to represent service domain data.
|
Name |
Type |
Description |
|---|---|---|
|
Name |
string |
The name of the unit. |
|
Description |
string |
The description of the unit. |
|
Symbol |
string |
The textual symbol of the unit. |
|
StepSize |
long |
The step size of the unit. |
|
UnitType |
EntityReferenceData |
Reference by ID to the unit’s type. |
None.
In order to integrate CA Business Service Insight with customers’ existing ITPAM processes, CA provides the customized SOAP call ITPAM operators described in this section. All of the ITPAM operators described here are based on the CA Business Service Insight Open API.
To enable CA Business Service Insight to integrate with ITPAM, you must reconfigure the following sections of the BSI Open API Web Service and the BSI Web Server IIS configuration file “Web.config”.
Add basicHttpBinding for SSL
Add basicHttpBinding for SSL to the Web configuration file by uncommenting the basicHttpBinding block in the Web.config file.
Follow these steps:
<basicHttpBinding>
<binding name="UsernameAndPasswordForSoap">
<security mode="TransportWithMessageCredential">
<transport clientCredentialType="None"/>
<message clientCredentialType="UserName"/>
</security>
</binding>
</basicHttpBinding>
Enable httpsGetEnabled
Follow these steps:
<behavior name="SecureTransportForSoap"> <serviceMetadata httpGetEnabled="false" httpsGetEnabled="true"/>
Note: There are two services in this serviceMetadata tag.
<behavior name="SecureTransportForSoap"> <!--<serviceMetadata httpGetEnabled="false"/> -->
Note: There is one service in this serviceMetadata tag.
Add endpoints for services
For each service, add https endpoints by uncommenting the httpsBinding endpoint in the Web.config file.
Follow these steps:
Note: The text doing the commenting is:
<!--“https configuration for ITPAM integration”
….
-->
Example:
This is a service before addition of https endpoints:
<service name="Oblicore.API.Implementations.Contract"
behaviorConfiguration="SecureTransport">
<endpoint
address="mex"
binding="mexHttpBinding"
contract="IMetadataExchange"/>
<endpoint
contract="Oblicore.API.Interfaces.IContract"
binding="wsHttpBinding"
bindingConfiguration="UsernameAndPassword"/>
This is the same service after unblocking the https endpoints (the commented elements are removed):
<service name="Oblicore.API.Implementations.Contract"
behaviorConfiguration="SecureTransport">
<endpoint
address="mex"
binding="mexHttpBinding"
contract="IMetadataExchange"/>
<endpoint
contract="Oblicore.API.Interfaces.IContract"
binding="wsHttpBinding"
bindingConfiguration="UsernameAndPassword"/>
<endpoint
address="mex"
binding="mexHttpsBinding"
bindingConfiguration=""
name="mexHttpsBindingEndpoint"
contract="IMetadataExchange" />
<endpoint
contract="Oblicore.API.Interfaces.IContract"
binding="basicHttpBinding"
bindingConfiguration="UsernameAndPasswordForSoap"/>
</service>
Configure the SSL connection for IIS
This section explains how to configure SSL connections for IIS.
Create a Self-signed Certificate for SSL
Follow these steps:
The Server Certificates dialog displays.
Add HTTPS Binding for IIS
This section explains how to add HTTPS binding for IIS.
Follow these steps:
The Actions pane displays.
The Site Bindings dialog displays.
The Add Site Binding dialog box displays.
SSL Settings
To enable http and https to visit BSI services, on both the site level and the API level, do not check “Require SSL” check box under SSL Settings.
Verify Certificate
Verify that the Open API certificate exists on your CA Business Service Insight Web server.
Follow these steps:
Example:
<serviceCertificate findValue="CN=Oblicore" storeLocation="LocalMachine" storeName="TrustedPeople" x509FindType="FindBySubjectDistinguishedName" />
The certificate name in the Web.config file is “Oblicore”. You must verify that an Oblicore certificate exists on the web and Therefore an “Oblicore” certificate exists on the CA Business Service Insight Web server.
The command console displays.
The Add or Remove Snap-ins dialog displays.
IIS restarts.
| Copyright © 2012 CA. Tous droits réservés. | Envoyer un courriel à CA Technologies sur cette rubrique |