Create the ION API service

Locate the template file: GENDIR/install/ionservice.xml.template

Open the file and save a copy as ionservice.xml.

Do not rename the file as templates should remain as delivered for future use.

Open the newly created ionservice.xml file and replace all variables enclosed in @ with the corresponding information from the LSF IOBox database created earlier in this process, as specified by the variable name.

The value of the LOGICAL_id variable is determined by the full logical ID defined in the LSF connection point created previously in this process.

@DATABASE_USER@
@DATABASE_USER_PASSWORD@
@DATABASE_NAME@
@DATABASE_SCHEMA@
@DATABASE_SERVER@
@LOGICAL_ID@

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.

<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>

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.

<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>

Verify that the changes you made to the file are correct and then save the file.