This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| 2500_config_apps:2300_external_sys_ldap [2026/08/13 01:10] – external edit 127.0.0.1 | 2500_config_apps:2300_external_sys_ldap [2026/08/13 04:21] (current) – repoint link to accordion panel cli |
|---|
| - You have a legacy system that you want to completely transfer to //**AwareIM**//. | - You have a legacy system that you want to completely transfer to //**AwareIM**//. |
| - You have an existing database software system(s) (or network server) and you want to continue using this system, however, you also want to add an extension to this system to be managed by //**AwareIM**//. | - You have an existing database software system(s) (or network server) and you want to continue using this system, however, you also want to add an extension to this system to be managed by //**AwareIM**//. |
| For the first scenario the recommended approach is to configure a new application using //**AwareIM**// and then transfer the operational data from the legacy database into //**AwareIM**// using [[3400_how_to:1100_miscellaneous:1360_import_export_date|Export/Import]]. For the second scenario you can get //**AwareIM**// to use the data stored in the existing database tables or network server by configuring business objects with persistence option ''Database: existing external'' or ''LDAP'' (see [[2500_config_apps:0500_add_edit_objects:0100_specify_gen_props|Specifying General Properties]]). With this approach you can configure new business objects managed automatically by //**AwareIM**// but also have business objects that will be shared between //**AwareIM**// and other software systems or network servers that already use the data. You can get //**AwareIM**// to write to the existing database tables or network servers or you can only perform queries on such objects. | For the first scenario the recommended approach is to configure a new application using //**AwareIM**// and then transfer the operational data from the legacy database into //**AwareIM**// using [[:3400_how_to:1100_miscellaneous#import_export_data|Export/Import]]. For the second scenario you can get //**AwareIM**// to use the data stored in the existing database tables or network server by configuring business objects with persistence option ''Database: existing external'' or ''LDAP'' (see [[2500_config_apps:0500_add_edit_objects:0100_specify_gen_props|Specifying General Properties]]). With this approach you can configure new business objects managed automatically by //**AwareIM**// but also have business objects that will be shared between //**AwareIM**// and other software systems or network servers that already use the data. You can get //**AwareIM**// to write to the existing database tables or network servers or you can only perform queries on such objects. |
| |
| When you define a business object with the ''Database: existing external'' or ''LDAP'' persistence options //**AwareIM**// will automatically import columns of the required database tables or data definitions of the network server and convert them into business object attributes. You will not be able, however, to add your own attributes to such objects(except shortcuts to reference attributes). | When you define a business object with the ''Database: existing external'' or ''LDAP'' persistence options //**AwareIM**// will automatically import columns of the required database tables or data definitions of the network server and convert them into business object attributes. You will not be able, however, to add your own attributes to such objects(except shortcuts to reference attributes). |