Create the ION API service

  1. Locate the template file: GENDIR/install/ionservice.xml.template
  2. Copy the template to a location on your server with the name ionservice.xml

    Do not rename the template file by removing "template" from the file name. Templates should remain as-delivered.

  3. Open ionservice.xml for editing.
  4. Make local updates.
    1. Replace occurrences of the variables (properties surrounded by ampersands as in @variable@) with the values shown in the example. These values are from the IOBox database.
      • @DATABASE_USER@
      • @DATABASE_USER_PASSWORD@
      • @DATABASE_NAME@
      • @DATABASE_SCHEMA@
      • @DATABASE_SERVER@
      • @LOGICAL_ID@
    2. If you use the Oracle database, change the value for the <dbtype> from the default of "msf" to "ora." Also verify that the <dbserver> and <dbname> properties are set appropriately and change them if they are not. In addition, you must update the server properties file, lsserver.properties. Oracle customers: Update lsserver.properties

      The example shows an updated ionservice.xml file. Note that <dbtype> is set to "ora."

      <xml? version="1.0" encoding="ISO-8859-1"?>
<BATCH_LOAD OVERRIDE="true" FORMAT="PLAIN TEXT">
  <SERVICE>
    <ID>LSFIONAPI</ID>
    <IdentityAttrList>dbuser</IdentityAttrList>
    <CredentialAttrList>dbpassword</CredentialAttrList>
    <SvcEntryAttrList>dbuser,dbpassword,dbtype,dbname,dbschema,dbserver,logicalid</SvcEntryAttrList>
    <HasCredential>TRUE</HasCredential>
    <LOGINSCHEME NAME="None"></LOGINSCHEME>
    <LoginProcedure>FILL_IT</LoginProcedure>
 </SERVICE>
 <IDENTITY SERVICENAME="LSFIONAPI" PRIVILEGED="TRUE" KEY="DEFAULT">
    <dbuser>DBUserAcmeCo</dbuser>
    <dbpassword>DBPWD1</dbpassword>
    <dbtype>ora</dbtype>
    <dbname>InforDB</dbname>
    <dbschema>dbo</dbschema>
    <dbserver>AcmeCoMingleServer.infor.com:1234</dbserver>
    <logicalid>InforLogicalID</logicalid>
  </IDENTITY>
</BATCH_LOAD>
    3. If you use the DB2 database, change the value for the <dbtype> from the default of "msf" to "ibm." Also verify that the <dbserver> and <dbname> properties are set appropriately and change them if they are not. In addition, you must update the server properties file, lsserver.properties. DB2 customers: Additional configuration steps

      The example shows an updated ionservice.xml file. Note that <dbtype> is set to "ibm."

      <xml? version="1.0" encoding="ISO-8859-1"?>
<BATCH_LOAD OVERRIDE="true" FORMAT="PLAIN TEXT">
  <SERVICE>
    <ID>LSFIONAPI</ID>
    <IdentityAttrList>dbuser</IdentityAttrList>
    <CredentialAttrList>dbpassword</CredentialAttrList>
    <SvcEntryAttrList>dbuser,dbpassword,dbtype,dbname,dbschema,dbserver,logicalid</SvcEntryAttrList>
    <HasCredential>TRUE</HasCredential>
    <LOGINSCHEME NAME="None"></LOGINSCHEME>
    <LoginProcedure>FILL_IT</LoginProcedure>
 </SERVICE>
 <IDENTITY SERVICENAME="LSFIONAPI" PRIVILEGED="TRUE" KEY="DEFAULT">
    <dbuser>DBUserAcmeCo</dbuser>
    <dbpassword>DBPWD1</dbpassword>
    <dbtype>ibm</dbtype>
    <dbname>InforDB</dbname>
    <dbschema>dbo</dbschema>
    <dbserver>AcmeCoMingleServer.infor.com:1234</dbserver>
    <logicalid>InforLogicalID</logicalid>
  </IDENTITY>
</BATCH_LOAD>
  5. Verify that the changes you made to the file are correct and then save the file. You are now ready to load the new service using the ssoconfig utility.