Configurng the OSB Project

  1. Open the sgg-osb-generic-adapter.zip file and extract the com.splwg.dg.sgg.osb.configuration.jar file into a temporary location on your hard disk.

  2. Ensure that OSB is running in the domain that is created for the adapter.

  3. Import resources by using the OSB Administration Console via the System Administration > Import/Export > Import Resources menu item from the extracted com.splwg.dg.sgg.osb.configuration.jar file. Note that conflicts may occur during import. They will be fixed in the following steps.

  4. Check and change the JCA Transport Configuration properties of the SGG-DG-CSV-CM/Proxy Services/InboundProxyService proxy service according to the deployment environment:

    Where:

    • Endpoint Properties/SGG_​INPUT_​PARSER is a name of class that implements file parsing functionality. See a Java project mentioned early.

    • Endpoint Properties/SGG_​ERROR_​FOLDER is a folder where a rejected transaction from incoming file will be placed in case when the parsing or validation is failed.

    • Endpoint Properties/SGG_​SP_​EXT_​REF_​ID is a value corresponding to the target Service Provider's external reference id on OUAF side. It is used in the XML structures related to the IMD & Event Upload Stats functionality. Also, this value will be placed into D1-InitialLoadIMD/serviceProviderExternalId and D1-DeviceEventSeeder/externalSenderId elements.

    • Activation Spec Properties/IncludeFiles is the naming convention that the Oracle File Adapter uses to poll for inbound files.

    • Activation Spec Properties/PhisicalArchiveDirectory is a folder where to archive successfully processed files.

    • Activation Spec Properties/PhisicalDirectory is an input folder to be polled.

  5. Change the Endpoint URI in the Transport Configuration section of the SGG-DG-CSV-CM/Business Services/DestinationBusinessService business service according to the deployment environment with value containing URI for JMS server and queue where IMD or Device Event structures will be sent (see Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus for more detail.):

  6. Change the Endpoint URI in the Transport Configuration section of the SGG-DG-CSV-CM/Business Services/NotificationBusinessService business service according to the deployment environment:

  7. Update the credentials stored in the SGG-DG-CSV-CM/Service Accounts/DestinationServiceAccount service account according to the deployment environment with user ID and password required to access JMS server:

  8. Repeat steps 4-7 for the SGG-DG-XML-CM project