Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Following are the steps to be followed in sequence to manage the entire process for configuring the POS Plugin:

Step #A: Configuring Plug-in Manager in Ginesys HO user interface

Step #B: MoP (Mode of Payment) configuration in Ginesys HO user interface

...

This section will be of a great help to the users who are expected to perform the configuration and deployment. The user of this document needs to expand each of the following steps in the sequence given:

Anchor
Configuring Plug-in Manager in Ginesys HO user interface
Configuring Plug-in Manager in Ginesys HO user interface

Expand
titleStep #A: Configuring Plug-in Manager in Ginesys HO user interface
  1. Under the Setup tab, click on the Plugin Manager under Configure section.

  2. Click on Add to start configuring a new Plugin Manager.

  3. Under the General tab enter the following for the required fields.

    The name of the Plugin Short Code is a sample name only. In real deployment, Plugin Short Code needs to be provided by Ginesys and the same needs to be set for the Plugin Short Code. Hence it would vary from payment partner to payment partner.

    Important - Please check the respective partners page for the Plugin Short Code and Plugin Assembly Name.
    Irrespective of brand, EaseMyRetail should be selected as Plugin Vendor .

    Target Config File Name: This is the original configuration file name as required by the plugin dll. File name should be without extension.

  4. Do the Hook Mapping.

    Info

    Note: Copy-Paste the following values (to avoid typo) for the respective fields:
    Hook Type : POS_PAY_PROCESS
    Class Name : PaymentProcessor (Ginesys to provided this. Hence it will vary from partner to partner)
    Method Name : ProcessPayment (Ginesys to provided this. Hence it will vary from partner to partner)


    Tip

    Important - Please check the respective partners page for the Class Name and the Method Name.


  5. Move to the Config Files tab to specify the config file name.

  6. Click on the Add Row button to add a new row.  By clicking on the Add Row button, multiple configuration files can be added one after another. However any one can be marked as “Is Default”.

  7. Scroll to the right to find the Browse button for the newly added row.

  8. Enable the Is Default option.

  9. Click on the Browse button.

  10. Select the config file called app.config (this is a generic/sample configuration file).

  11. Click on the Upload button and then click on the OK button.

  12. Assign the site. The process is similar to how the site has been moved from the list of available site to the list of assigned site box.

    Info

     In the “Site Allocation” tab and under the “Assigned Sites” list, the site against which the “Config File” column is blank for that the default configuration file (the one which has been selected for “Is Default”) will be considered. But if for an allocated site, the “Config File” column has a file name, that specific configuration file would be considered.


  13. Click on the save and close button at the top to save the Plugin Manager configuration.

  14. The configured Plugin Manager will now appear in the list of configured plugin managers.

    Plugin Manager configuration is now completed.

...