Associating an SSL client identity with a registry client

There can be more destinationConfig elements. A destinationConfig element is used to associate a particular SSL client identity with a set of destinations. It contains: • alias in the server protected store. A key entry with the same name as the alias must exist in a servers Protected Store. This key entry represents security material used to establish SSL with a destination server. The Oracle Service Registry server Protected Store is in the confpstore.xml file of a registry deployment package. Use this file when importing a key entry from a java keystore, as shown in Section 9.1, SSL Tool Examples . • password_coded element, which contains the encrypted password that is used to access a private key stored under the alias supplied. See Section 9.1, SSL Tool Examples for an example that prints out the encrypted form of a password supplied in plain text. • One or more destination elements each specify a rule. The rule can contain url or proxyName attributes. The rule matches when a client use a proxy class specified by the proxyName attribute or connects to a URL that is specified by the url attribute. The value of the url can end with a wildcard to specify a match of all URLs that start with the string specified before the wildcard. The whole destinationConfig element matches if at least one rule matches. The first matching destinationConfig is used. Page 385

9.2. Associating an SSL client identity with a registry client

Page 386 Developers Guide The Developers Guide is divided into the following main parts: • Mapping of Resources covers registering various XML resources in Oracle Service Registry including WSDL definitions, schemas, and transformations. • Client-Side Development describes the basic principles of using Oracle Service Registry APIs. For each client API, there is a comprehensive description of data structures and operations including links to JavaDoc, XML Schemas and WSDL documents. • Server-Side Development discusses how to access server-side APIs, including custom modules, interceptors, external validation services, and subscription notification services. The Oracle Service Registry web framework is also described in this section. • UDDI From Developer Tools discusses how to access UDDI from Oracle JDeveloper and Microsoft Visual Studio .NET. • How to debug describes logging and using the SOAPSpy tool.

1. Mapping of Resources

Oracle Service Registry provides you with functionality to register the following resources: • WSDL definition • XML file • XML Schema XSD • XSL Transformation

1.1. WSDL

This describes how to publish a WSDL file to Oracle Service Registry. The implementation reflects the OASIS UDDI technical note Using WSDL in a UDDI Registry, Version 2.0 [http:www.oasis-open.orgcommitteesuddi-specdoctn uddi-spec-tc-tn-wsdl-v202-20040631.htm]. As shown in Figure 1 , the technical note suggests a mapping between WSDL and UDDI. Page 387 Figure 1. WSDL TO UDDI

1.1.1. WSDL PortTypes

As shown in Table 1, “WSDL portType:UDDI Mapping” , each WSDL portType maps to a tModel having the the same name as the local name of the portType in the WSDL specification. The overviewURL of the tModel becomes the URL of the WSDL specification. The tModel contains a categoryBag with a keyedReference for the type of WSDL artifact and the namespace of the WSDL definitions element containing the portType, as follows: • The type is categorized as portType. • The namespace is categorized as the WSDL binding namespace. Table 1. WSDL portType:UDDI Mapping UDDI WSDL tModel categorized as portType portType keyedReference in categoryBag Namespace of portType tModel name Local name of portType overviewURL WSDL location

1.1.2. WSDL Bindings

In similar fashion, as summarized in Table 2, “wsdl binding:UDDI mapping” , WSDL bindings are mapped to tModels created for each binding, with name of the tModel gathered from the WSDL binding local name and the overviewURL again being the URL of the WSDL specification. Again, the tModel contains a categoryBag, this time with the following keyedReferences: • The type is categorized as binding. • The namespace is categorized as the WSDL binding namespace. • A portType category on the binding is used to refer to the portType tModel that was created for the WSDL portType as described above. Page 388

1.1.2. WSDL Bindings