 | Draft article not currently submitted for review.
This is a draft Articles for creation (AfC) submission. It is not currently pending review. While there are no deadlines, abandoned drafts may be deleted after six months. To edit the draft click on the "Edit" tab at the top of the window. To be accepted, a draft should:
It is strongly discouraged to write about yourself, your business or employer. If you do so, you must declare it. Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
Last edited by SporkBot (talk | contribs) 3 months ago. (Update) |
| Initial release | 1995 |
|---|
Bassem.w.jamaleddine (talk) 06:35, 30 June 2024 (UTC)
IBM San Francisco Project (SF or SanFranciso) was started in March 1995 and released on August 1997. As WebSphere v4 (supporting J2EE 1.3) was released in 2001, IBM put an end to the San Francisco Project.
SanFrancisco was a shareable framework that consists of distributed objects infrastructure and a set of application business components. IBM SanFrancisco is a stack framework that is build on three layers of reusable code written in Java that can be altered and expanded by application server developers. The stack consists of three layers:
– At the bottom, the foundation layer infrastructure that run as services to provide: transactions, collections, administration, and conflict control.
– Common Business Object Layer that provides implementations of business objects that are common to more than multiple domains
– Core Business Process layer that provides business objects and default business logic for selected domains: warehouse management, order management, accounts receivable, accounts payable, and general ledger.
Design
edit