Oracle EBS direct database access - oracle-ebs

We have a client who are using Oracle EBS. They would like to build some API to retrieve the data from Oracle EBS database through JDBC directly, and read the data through the API and insert into another database for another mobile application. Do we need to buy another Oracle EBS name user license? Or we just need to buy one Oracle database user license.
Why I asked this, because in SAP world, it seems directly access database will need per access name user license. Not sure, it is the same in Oracle EBS.
Please advice, and correct me if anything wrong.
Best regards,

You should have them talk to their sales rep. Generally, the Oracle database is licenced on a CPU basis (not named user basis). But there are certain technology features that may only be licensed for EBS use.
It sounds like you are using a different user to access data, which is the correct approach from a security perspective. Make sure that that database user has only the database privileges required to extract the data the application requires (least privs).

Related

iOS - use Aceess database and sharepoint to push and pull data

Currently I am creating app that needs to store and pull data from database by multiple users.
Since I do not have much knowledge in database, MS Access, and MS Sharepoint, I would like to know if it is possible to use share point as database for my iOS application, which implemented in pure swift code.
Any one with knowledge in this field please help me by providing advice on if it works, and, if possible, how can I successfully implement this.
Thank you for all the helps.
I don’t see why this would not work. As long as the SharePoint tables follow the rules for Access, then you can place the ms-access application on each desktop. Anytime “any” user of that application updates or adds records, then all other users will “eventually” see the updates. So in this setup, the desktop users can in fact “run” the application “off line”. The instant such users get Wi-Fi or a connection (or always have one), then the data is synced in real time.
The above setup takes no coding and is part of the Access system which supports those SharePoint tables.
As for the iOS and that part of the application? Again, I see little problem since all of the abilities of SharePoint are available as a web service. So as long as your development platform supports standard web services, then your application can interact with that web service to retrieve and update rows of data in those SharePoint tables. As noted, the “sync” to the Access clients will thus reflect any updates to that data.
Since near every modern phone development system supports interaction with web services, then the phone software can do the same. You not have an ODBC like interface, but you can query the data (CAMEL).
The Access desktop client will also be interacting with the SharePoint tables via a web service, but from Access point of view the SharePoint tables (lists) look like any regular SQL like table. So standard VBA code and DAO reocrdsets are supported.
The web services for SharePoint are outlined here:
https://msdn.microsoft.com/en-us/library/ms479390(v=office.12).aspx
And this video shows how you can upload data to SharePoint from Access, and NOTE how the relational table ability of SharePoint is supported by Access. Once that data is uploaded, then Access supports updating of such data as if the data was a local table.
https://www.youtube.com/watch?v=3wdjYIby_b0&list=PL27E956A1537FE1C5&index=2
You can use a single office 365 account at $6 per month for the above, and that single account supports 500 free users. So if you don’t have SharePoint (or don’t want to bother with SharePoint, a single office 365 account also offers these SharePoint services for that one stupid low price of $6 per month – and that account with work with the free Access runtime that that you can use to run the Access side for free on the desktop part of this application.

open office database password protection

I have a question regarding password protection to a table I created when I developed my database using Open Office.
I want to know how can I make a single table as password protected?
eg,
I have a database named Data
I created a table named Data-table
How can I provide a password protection on this table in open office?
In any database, access permissions are granted to specific database users. So in the initial OpenOffice Base connection setup you need to choose a specific user. (If you do not choose a specific user, the default is the SA account which has rights to all tables.)
To grant access, you need to execute a GRANT statement for that user. Examples using mysql are given at http://dev.mysql.com/doc/refman/5.7/en/grant.html:
GRANT ALL ON db1.table1 TO 'jeffrey'#'localhost';
If you are using the default HSQLDB engine with both the client and database in a single file, then in order to connect as a specific user, I think you need to convert it to a more powerful client/server setup.
To do this, you can either unzip the .odb file and extract the HSQLDB files (see here), or copy the data into a mysql database or other database of your choice. Once the data is in a separate database, it should not be hard to do what you are asking.

Data Shrink in QuickBooks web connector with ASP.net

I am using QuickBooks web connector and want to show company data(which is in QuickBooks ) in the web application for that I created a service which is communicating with web connector and getting all the data.
And for doing it I think I have to create a local DB where I can store all the data. Is it correct approach ?
If yes then How can I shrink QuickBooks data with my local DB
If No then what need to in this case
I am new in QuickBooks Please help me out
Thanks in advance
If you are using the web connector, you can't control when your service will be called. So there is a need to store the data somewhere; otherwise you may not have any data to display when your user logs in. Your idea to use a database as a repository for data is an approach that has wide acceptance in the domain of interactive web sites and beyond.
If the source of your data is one or more QuickBooks company files, it is extremely unlikely that you will have a need to shrink your data. The maximum size of a company file is orders of magnitude below the storage capacity of modern database systems, and 1TB hard disks currently retail for around $100US.
For the sake of overall efficiency and maintainability, it is a good idea to query for and store only the data your application needs. Learn how to use the IncludeRetElement qbXML element in your requests to filter the data that is returned from QuickBooks.

WIF - Federated Provider with multiple Identity Providers - store IP info in db?

So despite the warnings, I think I need to build a custom STS. We will support an arbitrary number of customers who provide identity information via SAML.
What is the best practice to store details on each IP? Most examples seem to store this info in the STS's web.config. That seems like it wouldn't scale real well.
Is there an obvious reason not to just store this stuff in a db and load it when the requests come in?
Fundamentally, if the Identity Providers will change over time, such as via some online administration function, rather than a new application deployment, it makes total sense to store the information in a database (or other Storage).
I think this is a potential issue for any multi-tenanted service that is federating identity with the customer.
ADFS v2.0 (which is Microsoft's STS product) stores its details in either a SQL Server DB (or SQL Server DB farm) or a Windows Internal DB. So if it's good enough for Microsoft ...

Suggestions for a practical User Authentication System?

I hate to re-invent the wheel so I'm looking for an existing solution to create a simple authentication system for my application. I've experimented for a while with using CardSpace or OpenID inside the application but I can't convince management that these would be working solutions.
Of course, I could just build a simple login dialog where username, domain and (hashed) password is stored inside a database table and I've done such a thing many times already. I hate this solution since I feel it's just a weak option. And I don't want to spend too much time trying to make the whole logon system as secure as possible, especially since I suspect that there should be existing solutions for this.
So, next to OpenID/OpenAuth and CardSpace, are there any other Authentication solutions that can be used from a Delphi/WIN32 application?
Right now, the application will be used by many customers. Most are single-user environments, although it's likely that some of those will start to have two to 5 users once this authentication system is added. But we want to support a customer who needs to allow about 500 different users on the same application. These are spread over about 100 offices but they all connect to the same SQL Server database. (MS Access right now, but we're making it possible for this user to use SQL Server instead.) To make matters even more interesting, the customer uses Citrix to centralize the user systems and the application has straight access to the SQL Server database. It's not an ideal setup but then again, the customer isn't really paying for this. We're just setting up a test environment. A proof-of-concept which the customer will test for us. Flaws will be solved later on. But right now I need quick solutions and one of them is a practical authentication system where I don't have to write a lot of code.
Have you considered using SQL Server authentication and not allowing authentication for those using an Access Database?
If you use the new SQL Server Native Client and SQL Server 2005 you can have passwords expire and change them from your client application. All of the tools to create and manage user accounts are built into SQL Server Management Studio. And if you decide later to support Windows Authentication you just need to modify your connection string.
We have a system where users on the network use Windows Authentication so they don't need to worry about another user name and password. For users that access the system via a VPN and non-domain joined machines they use SQL Authentication.
Here is the MSDN Page that talks about dealing with passwords programmatically in SQL Server 2005
You do need to make sure that SQL Server Native Client is installed, but that is simple compared to the rest of ADO.
I would suggest then
Delphi - since you are using Delphi :)
Open source - since you need to be able to figure out what is wrong if there is a problem, you probably want it cheap.
So, here are some solutions:
http://www.torry.net/pages.php?id=313
CoWindowsAccount v.1.0
SSecurity v.1.2.1.3
http://free-password-manager-plus.software.informer.com/1.6/
It might work for your purposes, but why not ask Windows for the current domain and user name, and use them as unique IDs. Windows has already done the authentication, and it saves the users making up new passwords or anything. I've used this to good effect. I also made it optional to include the machine name in the ID, so that the same user on different computers would also be unique.

Resources