Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| 3400_how_to:0900_other_systems [2026/08/13 00:55] – ↷ Links adapted because of a move operation localdev | 3400_how_to:0900_other_systems [2026/08/13 07:43] (current) – Imported by DokuWiki Advanced Plugin aware_support3 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Integration With Other Systems ====== | ====== Integration With Other Systems ====== | ||
| - | ===== How To... ===== | + | ===== How to... ===== |
| - | {{simplenavi> | ||
| - | < | + | |
| - | <panel type=" | + | < |
| - | </panel> | + | < |
| - | <panel type="primary" title=" | + | <accordion-item |
| + | This is explained in detail in the “[[2500_config_apps: | ||
| + | </accordion-item> | ||
| + | <anchor id="use_data_from_several_existing_database_tables"> | ||
| + | < | ||
| Sometimes you may want to connect to existing database tables but display data from several existing database table in a single query. With normal // | Sometimes you may want to connect to existing database tables but display data from several existing database table in a single query. With normal // | ||
| - | A better approach, however, is to define a view in the existing database that would select data from different tables, and then create a special // | + | A better approach, however, is to define a view in the existing database that would select data from different tables, and then create a special // |
| - | <panel type="primary" title=" | + | <anchor id="integrate_a_credit_card_payment_system"> |
| + | < | ||
| Many credit card payment systems, such as PayPal, require that your web site communicate with them via a particular URL. Whenever your web site needs to perform credit card payment the users need to click on the link with this URL, which will bring them to the web site of the credit card payment system. As part of the URL that your web site supplies to the credit card payment system you must also specify the URL that the credit card payment web site will use to return to your web site upon successful or un-successful completion of the payment. | Many credit card payment systems, such as PayPal, require that your web site communicate with them via a particular URL. Whenever your web site needs to perform credit card payment the users need to click on the link with this URL, which will bring them to the web site of the credit card payment system. As part of the URL that your web site supplies to the credit card payment system you must also specify the URL that the credit card payment web site will use to return to your web site upon successful or un-successful completion of the payment. | ||
| Line 24: | Line 28: | ||
| REQUEST SERVICE ProcessPayment of PayPalSystem USING PayPalPayment </ | REQUEST SERVICE ProcessPayment of PayPalSystem USING PayPalPayment </ | ||
| - Define a menu item that will start the above process – see the “[[2500_config_apps: | - Define a menu item that will start the above process – see the “[[2500_config_apps: | ||
| - | </panel> | + | </accordion-item> |
| - | <panel type="primary" title=" | + | <anchor id="expose_a_web_service_rest_ful_or_soap"> |
| + | < | ||
| // | // | ||
| All the details are explained in the “[[2500_config_apps: | All the details are explained in the “[[2500_config_apps: | ||
| - | </panel> | + | </accordion-item> |
| - | <panel type="primary" title=" | + | <anchor id="consume_a_web_service_rest_ful_or_soap"> |
| + | < | ||
| If you want to use an existing web service implemented as REST or SOAP then you need to do the following: | If you want to use an existing web service implemented as REST or SOAP then you need to do the following: | ||
| - Define an intelligent business object representing the web site exposing the web service – see the “[[2500_config_apps: | - Define an intelligent business object representing the web site exposing the web service – see the “[[2500_config_apps: | ||
| - | - Define REST or SOAP communication channels for this object as explained in the “[[2500_config_apps: | + | - Define REST or SOAP communication channels for this object as explained in the “[[:2500_config_apps: |
| - Define a rule that will request the service of the business object using the '' | - Define a rule that will request the service of the business object using the '' | ||
| - | </panel> | + | </accordion-item> |
| - | <panel type="primary" title=" | + | <anchor id="register_awareim_application_in_facebook"> |
| + | < | ||
| In order to allow users to login via Facebook you need to register your AwareIM application with Facebook. In order to do this: | In order to allow users to login via Facebook you need to register your AwareIM application with Facebook. In order to do this: | ||
| Line 51: | Line 58: | ||
| [[http:// | [[http:// | ||
| - | * Copy application id and secret that Facebook should assign to your application – you will need these when setting up login options (see [[3400_how_to: | + | * Copy application id and secret that Facebook should assign to your application – you will need these when setting up login options (see [[:3400_how_to: |
| When users login to your // | When users login to your // | ||
| [[http:// | [[http:// | ||
| - | </panel> | + | </accordion-item> |
| - | <panel type="primary" title=" | + | <anchor id="register_awareim_application_in_twitter"> |
| + | < | ||
| In order to allow users to login via Twitter you need to register your AwareIM application with Twitter. In order to do this: | In order to allow users to login via Twitter you need to register your AwareIM application with Twitter. In order to do this: | ||
| Line 71: | Line 79: | ||
| [[http:// | [[http:// | ||
| - | * Copy consumer key and secret that Twitter should assign to your application – you will need these when setting up login options (see [[3400_how_to: | + | * Copy consumer key and secret that Twitter should assign to your application – you will need these when setting up login options (see [[:3400_how_to: |
| When users login to your AwareIM application they should use the following URL: | When users login to your AwareIM application they should use the following URL: | ||
| [[http:// | [[http:// | ||
| - | </panel> | + | </accordion-item> |
| - | <panel type="primary" title=" | + | <anchor id="register_awareim_application_in_google"> |
| + | < | ||
| In order to allow users to login via Google you need to register your // | In order to allow users to login via Google you need to register your // | ||
| Line 92: | Line 101: | ||
| [[http:// | [[http:// | ||
| - | * Copy client id and secret that Google should assign to your application – you will need these when setting up login options (see [[3400_how_to: | + | * Copy client id and secret that Google should assign to your application – you will need these when setting up login options (see [[:3400_how_to: |
| * If using synchronization with the Google Calendar make sure that access to the calendar API is allowed! | * If using synchronization with the Google Calendar make sure that access to the calendar API is allowed! | ||
| When users login to your // | When users login to your // | ||
| Line 98: | Line 107: | ||
| [[http:// | [[http:// | ||
| - | </panel> | + | </accordion-item> |
| </ | </ | ||