Reg: WPC application architecture document

Hi,
We are looking for extending the WPC (Portal 7.3) features...
Is there any documentation around the new WPC (Portal 7.3 )application architecture where we can find the UI classes and services/backend classes api to publish the documents,creation of folders,creation of area and etc..
We know that below interfaces are available to extend the WPC, but we are looking more than this.
com.sap.portal.wpc.api.content
com.sap.portal.wpc.api.content.handler
com.sap.portal.wpc.api.content.provider
Thanks & Regds,
JC

Similar Messages

Best use of framework events in application architecture

Hello,
I apologize in advance if this is not the appropriate forum to be posting about Flex framework questions. I considered the Cairngorm forum, but thought the question applied more broadly to all flex frameworks. That, and it seems that the Cairngorm forum isn't really very active.
My question is about using frameworks for application architecture. Reading the "Introducing Cairngorm" document, I see that it specifically says that Cairngorm events are just those events that will handle business logic (things like grabbing data from a server, committing data to a server, etc). So then, how does a view interact with a controller when changing state?
Let's say I have two or three different views of the same data and I have a buttonbar to switch to the view I want. Is it then typical to dispatch a Cairngorm (or Mate/Swiz/Pure MVC, etc..) event to the controller to change the view state of the application? Does this effectively mean that for every button a user can click on, we'll have an event and a command associated with that event to perform some change of state or business logic? With a moderately complicated application, with several different screens, a few forms, a couple of lookups, i.e. lots of buttons for user input, that seems like an awfully huge number of events/commands...? Or do you dispatch a regular old flash Event to handle this? Or does the view data bind to the model to change the view state?
Obviously there's never any single correct answer to application architecture questions, but I'd like to know if there's any general best practices that I should follow. I don't want to under-architect OR over-architect my app. I'm new to Flex programming and would like not to code something egregiously ugly.
Thanks,
Cory

Hi,
Consider this, there is no such thing as an enterprise level RIA, the whole concept behind thin client was to restrict the enterprise requirements to the backend, that being said if we assume that a flex application is specifically for the client end and can maintain its own state and that MVC frameworks are more about enterprise solutions then the whole framework argument becomes what it is, academic BS.
<start rant>
Its really simply, in half a century nothing has changed, you have rules and requirements(model), you have access to that(view) and you wrap it up as a program/application(controller) so why do you need convoluted multilayer abstraction of functionality to make things work ? maybe so those that can't get a real development job can run around and preach at conferences, how else could they feed their adopted kids.
So all those nice buzzwords, design patterns(the new age terminology for modular architecture), model/view/controller, borg coding(resistance is futile) is all very fine if you want to act smart but producing quality code actually means you are smart. As you may have guessed I am not a strong proponent of MVC frameworks, and I don't even need to get into the argument that everytime a 'framework' expert gets control of a project that isn't done in their MVC poison of choice it gets a rewrite, clients really love those associated costs and retesting requirements.
</end rant>
You only need 1 framework for flex and thats the flex framework.
Have a read this blog, the section on MVC and Flex is very interesting if not overly polite.
http://www.herrodius.com/blog/216
David

Creating an Architecture Document For a Portal

I have been asked to come up with an Architecture Document for a public facing SharePoint 2010 site. I am familiar with the SharePoint 2010 technologies, however I need a starting point on where and how to start the Architecture document. Is there any Architecture Template Document that exists so that I can use them?

Hi
I cannot share the full and final doc with you but following Index will help you creating the Architecture document from the scratch
1     Document Overview............................................................................................................ 7
1.1     Scope............................................................................................................................... 7
1.2     Audience......................................................................................................................... 7
2     Logical Architecture............................................................................................................ 9
2.1     Overview.......................................................................................................................... 9
2.2     Diagram........................................................................................................................... 9
2.3     Component Description.............................................................................................. 9
3     Physical Architecture....................................................................................................... 11
3.1     Overview....................................................................................................................... 11
3.2     Production Environment.......................................................................................... 11
3.2.1     Diagram................................................................................................................... 11
3.2.2     Component Description....................................................................................... 12
3.2.3     Hardware Requirements...................................................................................... 14
3.2.4     Software Requirements........................................................................................ 14
3.3     Staging Environment................................................................................................. 14
3.3.1     Diagram................................................................................................................... 15
3.3.2     Component Description....................................................................................... 15
3.3.3     Hardware Requirements...................................................................................... 15
3.3.4     Software Requirements........................................................................................ 16
3.4     Development & Test Environment......................................................................... 16
3.4.2     Diagram................................................................................................................... 16
3.4.3     Component Description....................................................................................... 17
3.4.4     Hardware Requirements...................................................................................... 17
3.4.5     Software Requirements........................................................................................ 18
4     Non-Functional Requirements....................................................................................... 19
4.1     Security......................................................................................................................... 19
4.1.1     Requirements......................................................................................................... 19
4.1.2     Authentication........................................................................................................ 19
4.1.3     Authorization.......................................................................................................... 19
4.2     Availability..................................................................................................................... 21
4.2.1     Requirements......................................................................................................... 21
4.2.2     Hardware Redundancy and Failover................................................................. 22
4.2.3     Scaling Logical SharePoint Components......................................................... 22
4.2.4     Disaster Recovery.................................................................................................. 22
4.3     Performance................................................................................................................. 23
4.3.1     Requirements......................................................................................................... 23
4.3.2     Performance & Capacity Expectations.............................................................. 23
4.3.3     Size and Volume Assumptions.......................................................................... 23
4.3.4     Performance Testing Approach.......................................................................... 25
4.3.5     Performance Tuning Approach.......................................................................... 25
4.3.6     Monitoring and Reporting.................................................................................... 26
4.4     Accessibility................................................................................................................. 26
4.4.1     Requirements......................................................................................................... 26
4.4.2     Internal Access....................................................................................................... 26
4.4.3     Remote Access...................................................................................................... 26
4.5     Auditing & Reporting................................................................................................. 27
4.5.1     Requirements......................................................................................................... 27
4.5.2     Approach................................................................................................................. 27
4.5.3     Audit Reports.......................................................................................................... 27
4.5.4     Diagnostic Logging............................................................................................... 28
4.5.5     Portal Usage Reporting........................................................................................ 28
4.6     Exception Handling & Logging............................................................................... 28
4.6.1     Exception Handling............................................................................................... 28
       Application..................................................................................................................... 29
4.6.2     Logging.................................................................................................................... 29
4.7     Caching......................................................................................................................... 29
4.7.1     Disk based caching for BLOBs........................................................................... 29
4.7.2     Client-side caching............................................................................................... 30
4.7.3     Object Caching...................................................................................................... 30
4.8     Maintainability.............................................................................................................. 31
4.8.1     Backup and Restore.............................................................................................. 31
4.8.2     Archiving & Purging.............................................................................................. 32
4.9     Regional Deployment................................................................................................ 32
4.9.1     Conceptual Diagram............................................................................................. 32
4.9.2     Feature Summary.................................................................................................. 33
4.10      Service Management.............................................................................................. 35
5     Search Architecture.......................................................................................................... 36
5.1     Introduction.................................................................................................................. 36
5.2     Key Design Considerations..................................................................................... 37
5.2.1     Distributed Geographical Deployment............................................................... 37
5.2.2     Content Sources.................................................................................................... 37
5.2.3     Availability & Performance................................................................................... 37
5.2.4     Physical Infrastructure.......................................................................................... 38
5.2.5     Search as a Shared Service................................................................................ 38
5.3     Search Architecture in portal..................................................................................... 38
6     Content Deployment Architecture................................................................................ 41
6.1     Introduction.................................................................................................................. 41
6.2     Key Design Considerations..................................................................................... 41
6.2.1     Distributed Geographical Deployment............................................................... 41
6.2.2     Security.................................................................................................................... 42
6.2.3     Availability............................................................................................................... 42
6.2.4     Publishing Frequency.......................................................................................... 42
6.2.5     Physical Infrastructure.......................................................................................... 42
6.2.6     User Contributed Content.................................................................................... 42
6.3     Content Deployment in portal................................................................................... 43
7     References.......................................................................................................................... 45
8     Key Decisions.................................................................................................................... 46
9     Dependencies.................................................................................................................... 47
10      Key Contacts................................................................................................................... 48
11      Appendix A – Active Directory Requirements........................................................ 49
12      Appendix B – Capacity Sizing Model........................................................................ 51
13      Appendix C – Hardware & Software Requirement Summary............................. 53
14      Appendix D – Site Architecture................................................................................... 55
Regards
Deepak Aggarwal

Reg: oracle applications

Hi
am working in apps DBA , I want more detail about concurrent manager in oracle application. So will u please send me the any documents about concurrent managers.
Regards
Karthickraja

Duplicate post.
Reg:oracle applications
Re: Reg:oracle applications

Need to do a clean reinstall, but need to keep applications and documents

I know that to do a clean reinstall of 10.6 you must first erase the hard drive using Disk Utility. I want the reinstall to be clear of all old settings, except that I need to carry over my applications and documents. Could I use Migration Assistant to backup just the applications and documents to an external hard disk, reinstall the OS, and then use Migration Assistant again to restore my applications and documents from the external drive? I've never used Migration Assistant.

Why can't you just delete the current settings?
But if you really want to erase everything and reload 99.9% of it, use +Setup Assistant+ after you install OSX on the empty volume. By default, it will transfer your network settings, but you can omit them. See [Setting up a new Mac from an old one or its backups|http://web.me.com/pondini/AppleTips/Setup.html] (or use the link in *User Tips* at the top of the +Snow Leopard > Installation and Setup+ forum).

Oracle ERP and CRM Application Architecture Direction

Not sure if this is out of topic for this forum but it seemed the closest I could find. If it is out of topic could someone please point me in the right direction?
Im looking for the architectural direction Oracle is taking for their ERP and CRM applications. Specifically as Oracle moves their applications to the Oracle 9iAS application server will Oracle be changing their application architecture to a Service Oriented Architecture (SOA) as other ERP and CRM vendors are? If not what architecture will the Oracle applications follow?
Phil Montagliano
Xerox Corporation
XIM/Technology, Strategy & Architecture
161 South Chestnut Street Email: [email protected]
One City Centre / 0875-05B Phone: (585) 423-8831
Rochester, NY 14604 Fax: (585) 423-4848

Hi,
bit confuse about your question. are you looking for techniacal architecture or looking for business prospective?
Kindly elaborate your question.
Yogi
[email protected]

ADF Application Architecture

Hi All,
I am new to ADF and working with some vendor to transform our in-house Oracle Form Application to ADF Application and we have more than 300 Oracle Forms to translate.
Basically after the login page, we will have a main menu, and then from the main menu, user can access to different modules (e.g. Customer Profile / Supplier Profile / Order Processing etc..). One of the critical point is that there will different shared variable pass from the main menu to each module and from each module back to the main menu.
We have successfully translate a few Oracle Form to ADF JSF Application. However, before continue the project, we would like to confirm the application architecture.
Checking on Oracle Website / different ADF forum, basically they will packaging all their ADF program in 2 different approach.
Approach (1):
i) Create a common workspace which put all the common EO, VO, AM, Task Flow Template, Page Template, Skin, etc and export as an ADF Library
ii) Create different Bounded Task Flow Workspace with its corresponding Model and View Controller for different modules (e.g. Customer Profile / Supplier Profile / Order Processing etc..) and then export as an ADF Library
iii) Create a master workspace with View Controller to contains an Unbounded Task Flow to tier all the different modules together as an EAR file.
Approach (2)
i) Create a common workspace which put all the common EO, VO, AM, Task Flow Template, Page Template, Skin, etc and export as an ADF Library
ii) Create different workspace with its corresponding Model and View Controller for different modules (e.g. Main Menu / Customer Profile / Supplier Profile / Order Processing etc..) and then export as an EAR file
From Approach (2), when I need to pass parameter from Main Menu to Customer Profile, since they are from different application, I can only pass it through URL or database. But it seems to be not a very approach. May I know is there other way to passing parameter between different ADF Application ?
From Approach (1), it seems that the parameter can be passed using the bean since they are under one master workspace. However, from some of the forum said, if there is too many modules (my case is ~ 300 modules, there will be a problem on the CPU, RAM and JVM may not be able to start.
May I know is it correct from my assumption ? Also may I know which approach should I use ? Thanks !!
Best Regards,
Eric

Hi Timo,
Thanks for your reply. Yes I have watch the ADF Architecture TV Episode too. But I still cannot figured out which approach I should using. From the video, it said that sum of the parts may risk from the start up of JVM when you have too many application. Pillar architecture can solve that problem however parameter may need to pass through different ADF application since they are compiled as different EAR file. But passing the parameter through URL / database package seems not an excellent idea.
Moreover, since all those ~300 modules are different and may not related from each other, so it may not be a suitable case to put multiple forms into one ADF application in my case. Also our system have frequently change request from the user and those request are usually handled by different developer. So I guess it may be better to put it in different ADF application instead of putting in a single one.
Any advice ? Thanks !
Eric

Define Workstation Application per document type

Hello friends
Is it possible to restrict some worstation application per document type?
I mean, for a specific document type only XLS files are allowed?
Thanks in advance
Luis Ike

Hi Luis,
yes you can define it in the customizing:
Logistics - General - Product Lifecycle Management (PLM) - Document Management - Control Data - Define Document Types
Select a document type and check details. There you can define a default WS application.
If you define it to XLS and you do not assign XLS to any other document types then I think you can reach what you want.
Best regards
Tamas

XI Architecture document

I would appreciate if anyone can send me the XI architecture document that you guys used for real XI implementation at the customer/client site. I surely would reward with points.
Pam

If you are looking for ASAP of SAP XI this link should help you - http://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_XI/index.htm
but in case you are looking at the Xi arch. in terms of its connectivity and build - https://websmp205.sap-ag.de/xi

ERP and CRM Application Architecture Direction

Not sure if this is out of topic for this forum but it seemed the closest I could find. If it is out of topic could someone please point me in the right direction?
Im looking for the architectural direction Oracle is taking for their ERP and CRM applications. Specifically as Oracle moves their applications to the Oracle 9iAS application server will Oracle be changing their application architecture to a Service Oriented Architecture (SOA) as other ERP and CRM vendors are? If not what architecture will the Oracle applications follow?
Phil Montagliano
Xerox Corporation
XIM/Technology, Strategy & Architecture
161 South Chestnut Street Email: [email protected]
One City Centre / 0875-05B Phone: (585) 423-8831
Rochester, NY 14604 Fax: (585) 423-4848

Hi,
bit confuse about your question. are you looking for techniacal architecture or looking for business prospective?
Kindly elaborate your question.
Yogi
[email protected]

UDS Application Architecture Validation

Hi Everyone,
I am curious to find out if there are any tools that can validate the existing UDS application architecture. Especially is there anything within the UDS family - say a UDS parser - that we can use?
thanks in advance,
Vamsi.

There is at least one Consulting tool still in existence that can analyse Forte/UDS code and provide limited feedback on the architecture used, but it focuses more on syntax and things considered to be poor (or risky) coding. As far as I know, it was developed within Forte to assist their Consultants in the field. It requires a fairly high degree of Forte/UDS Architecture knowledge to use correctly and especially to make good use of the results.

Application architecture of oracle crm suite

Can anyone let me know where can i find the application architecture for oracle crm suite which includes oracle 3i and oracle 11i.

Hello -
First of all the best for your Thesis and appreciating for selecting Oracle BPM.
Check this : http://www.oracle.com/technetwork/middleware/bpm/obpm-articles-086639.html
Most of the articles are by Mariano Benitez - BPM Architect.
BR,
Justin.

How to organize project structure for big application architecture

Hi all:
We prepare to construct a medium erp project using JHeadstart,
so we have some application system like human resource, accounting, inventory, ...
What's the best suite to organize application project architecture ?
we have this issue about application architecture:
1.how to fulfill large scale application and must to share some common view object and entity object in all application, May we to break the application down into multiple BC4J packae in same project or separate each subsystem in each project folder?

You can definitely organize your applications into as many packages as makes sense for your overall design.
You can create and deploye packages of BC4J components in simple *.jar archives and then uses features of JDeveloper to import those shared packaged of components in a read-only mode in projects that need to make use of them.

My MacBook Air's storage is full. When I look at the storage, most of what is taking up the space is "other". I am not sure what these application or documents are but would like to reduce this so that I can store more pictures to edit. Any advice?

When I look at the storage, most of what is taking up the space is "other". I am not sure what these application or documents are but would like to reduce this so that I can store more pictures to edit. Any advice on how to find out what takes up this much space so that I can clear some off?

Freeing Up Space on The Hard Drive
1. See Lion's Storage Display.
2. You can remove data from your Home folder except for the /Home/Library/ folder.
3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
4. Also see Freeing space on your Mac OS X startup disk.
5. See Where did my Disk Space go?.
6. See The Storage Display.
You must Empty the Trash in order to recover the space they occupied on the hard drive.
You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.
What is "Other" and What Can I Do About It?- Apple Support Communities

Comment créer un «master» de styles qui s'applique à plusieurs documents?

Est-ce possible de créer un «master» de styles qui s'applique à plusieurs documents et qu'on peut ensuite modifier pour ajuster tous les documents en même temps? (un genre de CSS) J'ai des centaines de fichiers générés automatiquement qui eux contiennent chacun plusieurs fichiers différents, donc j'ai besoin d'un fichier central ou je peux gérer les styles.
SVP toute aide serait bien appréciée, merci!
JUliE

Bonjour JUliE,
si nous parlons de Dreamweaver:
si la structure doit être le même pour tous, vous pouvez utilisier des «templates» voir svp:
http://help.adobe.com/fr_FR/dreamweaver/cs/using/WScbb6b82af5544594822510a94ae8d65-7abea.h tml
si la formatage doit être le même pour tous, créer un style CSS comme modèle général, par exemple:
<link rel="stylesheet" href="css/VotreStyle.css" />
Hans-Günter

Reg: WPC application architecture document

Similar Messages

Maybe you are looking for