Sharing Aware's DB with other system

BenHayat

Hey guys;

I've seen some developers here have gone beyond using Aware's Data within Aware and use/share with it from other systems. So, please clarify some of my questions and concerns. This will be using MS SQL DB.
Suppose an application is created by Aware system, Aware is the owner and maintainer of that DB Schema.
I need to create a Web service server in ASP.Net Web API (using C#) that will respond to requests coming from "Native" mobiles, i.e. iOS.

1) The Native Mobile user (who is also a current user in Aware Desktop version) needs to login.
This means, when the Web Service gets the login request, it needs to find the user in Aware's User table and try to match the User ID and Password.
Q: How am I going to get the real value of the password that was stored by Aware's system to match what user has passed in? Another words, how can I decode the password that was stored by Aware in the DB to match the value sent by user?

2) Aware doesn't use Foreign and composite indexes. But in ASP.Net ORM (Entity Framework) it needs to use foreign indexes to find child records. Can I add these Indexes to the DB using SQL Studio and when I add or change new attributes to Aware's BO, will Aware delete/drop those Indexes or will leave them alone?

3) If the Web service needs new tables in that DB, should I create those as new BO in Aware or should I create the tables in the DB without the knowledge of Aware's system?

4) When Aware is working on a BO in the context, does Aware flag that record in DB being dirty and worked on? If yes, can you give me more info on the flag? And if yes, should the web service do the same thing to let Aware know the Web service is working on a dirty record?

5) Are there any other points to consider when sharing Aware's data with other systems?

Thank you in advance!

aware_support

1) You will need to perform an MD5 conversion of the password that the user has specified and then compare the resulting value with the values stored in the database

2) You can add whatever indexes you want - Aware IM will not touch them

3) It depends on how you will use the new table. If the table will only be used by the service, there is no point adding it to Aware IM

4) Aware IM starts a database transaction when it works with database records - there are no "dirty" flags

5) If your service is going to be creating records in the database it has to follow Aware IM conventions - increment BAS_IDGEN index, assign the ID, populate other fields that each Aware IM record has

BenHayat

aware_support wrote
5) If your service is going to be creating records in the database it has to follow Aware IM conventions - increment BAS_IDGEN index, assign the ID, populate other fields that each Aware IM record has

Thank you support for valuable answers.
Yes, I have to add/update/delete records in the service, as the mobile app will add new records.
Is there any documentation related to this subject to conform with Aware's data processing and making sure we update Aware's internal tables?

aware_support

There is no documentation, but it's quite straightforward. Increment the value in BAS_IDGEN, assign the new value to the ID of the new record, set it;s timestamp and version to 1

BenHayat

aware_support wrote
There is no documentation, but it's quite straightforward. Increment the value in BAS_IDGEN, assign the new value to the ID of the new record, set it;s timestamp and version to 1

Thank you;
Q: on maintaining relationships between tables:
And when adding new records that have relationships with other tables, I should just follow the same pattern as Aware does to fill in those columns that acts as pointers to other tables? (by looking at how Aware fills in those columns).
This way, Aware can continue using those columns for it's relationships and the .Net service can use Foreign indexes for it's relationships.