iSM 5.x releases required applications to define access to resources, such as a JDBC database or an LDAP server, in the components where the resource was used. In iSM 6.0, this access has been consolidated into named providers. Components using the service simply name the predefined provider to be used. This enables iSM to control the resource for integrity and performance more efficiently. Examples of providers include LDAP, keystore access, and database connections. Older services (agents) or listeners that controlled their own resources (such as requiring an SSL-based HTTP listener to specify the location of its keystore) continue to function as before. Many components have also been modified to use providers (either exclusively or as an alternative to the specific configuration of the resource) and new components all use providers. For example, the nHTTP listener uses providers exclusively. Some operations in iSM 6.0, such as the LDAP() function, operate only through providers.

While the advantages of providers are numerous, each provider must be configured (defined) before it can be used. As a case in point, any use of the LDAP function must specify either the default LDAP provider or a specific named provider. In iSM 6.0, many LDAP directories can be used, rather than the single one supported by the iSM 5.x release.

To assist in defining the required providers, the Migrate5 tool is provided. This tool can transfer settings from an iSM 5.x configuration into a newly defined iSM 6.x configuration.

The following components can be migrated using the iWay Migration Tools extension (iwxmigrate):

• User-defined configuration special registers.
• XML schemas.
• Retry time settings, trace settings, and iwse SOAP settings.
• 5.x LDAP configuration into a default provider.
• 5.x JDBC provider configuration into a default provider.
• 5.x SSL and SMIME keystore settings into one or more keystore (and truststore) providers. SSL and SMIME providers that reference the newly migrated providers.

This section describes the available migration tools that are provided with the iWay Migration Tools extension (iwxmigrate).

tool migrate5 <path to 5.x dictionary> [<path to output file>]

tool migrate5 c:/release5.6/config/base/base.xml c:/out.xml

tool migrate5 c:/release5.6/config/base/base.xml

tool comparefuncs [<parm1>] [-debug] [-parse] [-string]

funcs->set rega hello
stored
funcs->c:/a-b-sreg(rega)Tree60:<superroot>
   <arith>-
      <x-literal>c:/a</x-literal>
      <arith>-
         <x-literal>b</x-literal>
         <sreg>
            <x-literal>rega</x-literal>
         </sreg>
      </arith>
   </arith>
</superroot>
Tree56:
<superroot>
   <concat>
      <literal>c:/a-b-</literal>
      <sreg>sreg(rega)
         <p-literal>rega</p-literal>
      </sreg>
   </concat>
</superroot>6.0=NAN
5.6=c:/a-b-hellofuncs->

funcs->_concat('c:/a-b-',sreg(rega))Tree60:<superroot>
   <_concat>
      <x-literalc:/>a-b-</x-literal>
      <sreg>
         <x-literal>rega</x-literal>
      </sreg>
   </_concat>
</superroot>
Tree56:
<superroot>
   <concat>_concat(&apos;a-b-&apos;,sreg(rega))
      <p-literal>c:/a-b-</p-literal>
      <sreg>sreg(rega)
         <p-literal>rega</p-literal>
      </sreg>
   </concat>
</superroot>6.0=c:/a-b-hello5.6=c:/a-b-hellofuncs->

tool scanparms  <config | -file filename> [@reportfile]

Enter command:>tool scanparms fred
scanparms: review dictionary for minus---> settings/logroot,
stmt='sreg(a)-8'
scanparms: review dictionary for exist()---> listener=filein/parm1,
stmt='_exist('c:/abc')'
scanparms: review dictionary for minus---> listener=filein/maxcount,
stmt='sreg(a)-100'
scanparms: review dictionary for xpath/ns---> listener=filein/sregns,
stmt='xpath(/a:x)'
scanparms: review dictionary for xpath/ns---> listener=filein/sregsr,
stmt='xpath(/a:x/sreg(b))'
scanparms: review dictionary for xpath/sreg---> listener=filein/sregsr,                                                   
stmt='xpath(/a:x/sreg(b))'
Tool scanparms complete