Architecture Design for CORBA

hi,
i would like to know if it's possible to integrate CORBA afterwards in an application or do i have to make preparations in the current architecture if i decide that i want to use CORBA in my application?
thanks in advance.

wgctrey wrote:
thanks for you reply. i know that it depends on the design of the application and that i need a "good" design. but what is a good design to be prepared for CORBA?I wouldn't design for Corba. I would created a layered design where it doesn't matter if it's Corba at the lower layers.
Kaj

Similar Messages

Need best Architecture design for the following scenario

Hi Experts,
I need best architecture design for the following scenario:
Sender: Mail
Receiver: if sender body contain u201DApproveu201D, then call SOAP adapter, If SOAP adapter execute successfully, then send Mail(SOAP adapter executed successfully) and SMS . So receiver is SOAP, Mail and SMS.
My current approach issue:
Three message mapping:
Mapping1: mail to SOAP
Mapping2: mail to Mail
Mapping3: mail to SMS
In interface determinant>u201DSelect all three operation mappingu201D> u201Cselect order at runtimeu201D.
Issue in current approach: For me first SOAP adapter should complete successfully, after that only my Mail and SMS operation mapping should execute:
But problem is before success of SOAP adapter engine, Mail and SMS mapping completed or integration engine executed.
Note: There is possible to fail the SOAP request in adapter engine.
Kindly help me --> u201CAm I going correct way or want to change the architectureu201D?
Thanks for advance!!
Regards, Kumar

What do you mean by successful execution of soap call? Are you talking about Successful response (happy flow) from the soap call instead of application error ? Then based on the response you want to decide sending mail and sms. How big call is your soap ? If your soap interface is very simple I can give the other possible way.
Sender sends the message, use mapping to read the content and then do soap call in the mapping itself and after seeing the soap response decide about two receivers (mail and SMS). If your soap call is very simple one, you can go for it. Otherwise I would not recommend this. The reason is you loose some visibility regards to monitoring during soap call in the mapping.
Other option is go for CCBPM. Here you receive the message, use send step to soap interface which is sync step. Then after seeing the response create another block with fork steps each for two senders mail and sms. If response bad then dont proceed or execute the next block. Simply use exeception or control step to jump out from the block,

Architectural design for FTP batch processing

Hello gurus,
I would like your help in determining the design for the following.
We receive several HL7 messages as a text file and copied to a shared network folder. All these files are created into several different folders depending on the region, message type. We need to come up with a B2B process to read all the files from the netwrok folder using FTP (batch process) and translate if needed (depending on the scenario) and transfer the files over to other destination folder on the network (using FTP).
For this, we can create TPs with Generic FTP channel and this works without any issues. By doing this way, we need to create TP for each and every type of message which reads the files from its own specified directory location on the network based on the the polling interval.
My question is, instead of creating TPs for each and every type of file, is there a way by which I can write a common web service that reads the source files from the network and based on the type of the file route to the proper destination folders. If it is possible, I would like to know the architecture for accomplishing this task.
I really appreciate your kind help on this.
Thanks and regards,
Raghu

Hi Raghu,
Is it a B2B communication scenario?
By doing this way, we need to create TP for each and every type of message which reads the files from its own specified directory location on the network based on the the polling interval.Why cann't you have only one TP with multiple documents, channels and agreements?
My question is, instead of creating TPs for each and every type of file, is there a way by which I can write a common web service that reads the source files from the network and based on the type of the file route to the proper destination folders. If it is possible, I would like to know the architecture for accomplishing this task.Depends on your use case and products you want to use. You can very well use FTP adapter with BPEL and poll for files. Use DVM in composite to figure out the destination and send it there. You may use OSB if it is a typical routing case with heavy load and performance is a concern. You may use B2B as well here. So ultimately you need to figure out what you want and what tools you want to use.
Regards,
Anuj

Global Architectural design for SharePoint 2013??

Hi Friends,
i am trying to pursue SharePoint 2013 global Architectural design before we implement SharePoint 2013 farm. FYI, Our Current SharePoint 2010 farm is three tier farm (2 web servers + 2 App servers + cluster Sql server) and total users 1,000 and its
located in one data center. From this farm we are serving now SP site to five different countries in the world via WAN. But as our company growing rapidly, we want share point will provide robust performance. As our company globalized, how many data center
we will need? Can we have one centralized farm in USA and other regional SharePoint farms into different countries? According to my business scenario, what will be the best architectural design?
Any help will be appreciated!!

"It depends" would be the answer with the information given. It depends on how much content is accessed at any one location, if a WAN accelerator could alleviate any issues end users at the remote locations were seeing, and if the company can take on the
added complexity, extra licensing, and hardware cost that are associated with SharePoint farms.
It would also depend if you want to replicate content (e.g. Metalogix Replicator) or if each farm will have its own unique content targeted at the specific region.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

E-Recruitment Technical architecture design for stand alone

Hello,
I looking at various options to implement E-Recruiting in a stand alone scenario.
One option i know is where my HR Data is in ECC6.0 and E-Rec component is in other ECC6.0 system and i can interface the data through ALE and RFC's.
When we talk about E-Rec in standalone (without ECC), how would be technical architecture look like.
Please help me with some inputs.
Best Regards
G Raj

Hi Raj,
Am not sure what are the exact details that you require. I have given a few pointers which may be of use.
Incase eRecruiting is on a different server then the transfer of data (PA & OM ) will be through ALE & idocs.
The transfer of data from eRecruiting to ECC is through RFC where only a set of 15 fields can be transferred back. There is also a newer option to use XI for this.
The standalone server usually has only the erec component & no other HR module (Pls chk the installation guide on this point)
A few BADIs need to be activated in the erec server
When an internal employee(object P) is transferred here, a corresponding object NA(candidate) & BP(business partner) is created.(This is because of the BADI activation)
Incase of an external employee , the moment he registers, an object NA ,BP ,CP is created.When he is hired into the system, there is an object P created with a New CP which then will have to be coonnected to the original NA.
Change pointers will take care of synchronisation of data between both the servers.
The relationship between the various objects are seen in infotype 1001 in the erec system.
The advantage of using this scenario is that core HR is not exposed to external people as the erec server talks with the external world.
Incase of webdynpro ABAP as UI, you can have separate fron-end & back-end.
Regards,
Sowmya

Architecture/design for high volume web service calls from on Demand

Hi,
We have hundreds of end users (less than 600 users) that will be initiating web service calls from On Demand that will deal with both querying (stateful transaction) and inserting/updating data (stateless). Currently, we see a limitation on the number of stateless sessions (33) that can initiate web service calls. We are afraid this will lead to poor performance with the number of sessions that are allocated for stateless sessions.
Can someone provide any design or framework information that can be implemented for high volume web service calls from On Demand? We anticipate 35K+ web service calls that will be initiated from On Demand per hour.
Thanks.

Hi,
We have hundreds of end users (less than 600 users) that will be initiating web service calls from On Demand that will deal with both querying (stateful transaction) and inserting/updating data (stateless). Currently, we see a limitation on the number of stateless sessions (33) that can initiate web service calls. We are afraid this will lead to poor performance with the number of sessions that are allocated for stateless sessions.
Can someone provide any design or framework information that can be implemented for high volume web service calls from On Demand? We anticipate 35K+ web service calls that will be initiated from On Demand per hour.
Thanks.

Architectural design for a forum

using servlets, we need to design a web forum. Question: How would you design the interface for the webmaster. How do you archive the website content, modify content etc.

this is another test

Architecture advice for Effect and AEGP communication

Happy monday!
In my current plugin project I need to use an "helper" AEGP for tasks my main effect plugin cannot accomplish (delayed tasks via AEGP idle hook, project modifications that will crash if performed inside the Effect logic, etc.)
I'm trying to figure out an elegant and robust architecture design for this cross-communication.
Heres the way I see it:
Effect passes info along to AEGP via custom suite data.
AEGP reads the data at idle, and performs some required task.
The success/fail of this work and the resulting products are communicated back to the Effect via AEGP_EffectCallGeneric.
My question is basically surrounding the data/info handoff. What kind of objects should I be passing back and forth? Is it considered poor design to simply pass along a pointer to the sequence or custom arb data to the AEGP via the custom suite? And vice versa when the GP sends EffectCallGeneric to the effect and passes a pointer, it could just be the same pointer that the effect originally sent the AEGP using the custom suite.
Aside from undo/redo, is there an advantage to using arb parameter data over sequence data for this task?
It seems to me that AEGP plugins are loaded once and only once in the session, so if multiple instances of my effect plugin are used in the project, and they are all calling the AEGP there is the potential for a race condition if the custom suite data is used to pass along information. Is this an accurate assessment of AEGPs? A simple example of this would be that the custom data suite has a variable that stores which effect plugin is calling the AEGP. If another instance of the effect starts talking to the AEGP, it would overwrite the suite var telling the AEGP which effect instance is calling it, thereby making the AEGP perform the work of one effect instance but sending the results to different instance.
Even if the AEGP is extremely simple and just performs small atomic operations each time the custom suite data tells it to, how do I prevent n+1 Effect instances from colliding when using the AEGP worker? Am I missing some key part of the Effect->AEGP communication that prevents this race condition situation?
This is the first time I've tried my hand at writing inter-process communication where I have the option to exchange actual in-memory objects. I'm hoping someone with more experience with this sort of problem can give some pointers(hah) or at least a few cautionary words about designs to avoid.
Thanks, sorry for such an open ended question, but this is the place to talk to the pros
-Andy

yo andy! what's up?
i see you were up to no good... naughty.
you are correct in your assumptions.
AEGPs are indeed loaded only once per session, but if you're rendering with
the "multiple frame simultaneously" option, then the AEGP is loaded
separately for each AE instance.
(so would your plug-in. each AE instance calls it's own global setup)
now, plug-ins are called on the main thread. which should mean that only
one plug-in is is called at a time, which should mean that your AEGP may
only get one call at a time. i'm not absolutely sure that the base
assumption is correct here. it's possible that multiple effects are called
at the same time, so re-entrancy of your AEGP suite is possible.
how do we know? we can either test, or ask zac lam.
re-entrancy is a non issue when reading data (all can read at once. it
doesn't matter). but when writing data... that's a problem.
to prevent such issues you need to implement some mutex (mutually
exclusive) mechanism.
it only allows one caller access at a time, while the other caller stall
until their turn.
boost library offers such tools.
as for what data you should transfer.
you can either pass data by value, or by reference.
when a function gets it's data like so:
function(int val);
it get's a local copy of the data. no worries about scope here.
if it gets the data like so:
function(int *val);
or function(int &val);
then we're talking reference. in this case, the val variable is only valid
while the object to which it refers is valid.
that depends on stability of that memory chunk. what makes a chunk stable?
1. if the data is created as a local scope variable it will invalidate when
the code block finishes. make sure don't access that data at other times.
2. AE handles of a plug-in instance are only valid during calls to that
plug-in.
let's look at the two directions of communications you have.
1. effect calls AEGP.
in this case, the call order is as follows:
AE calls effect.
effect is now executing. at this point, sequence/global data are valid, and
anything locally allocated in the call handling function.
effect calls AEGP.
AEGP is now executing.
you can now pass anything you like from the effect to the AEGP.
if the AEGP returns data, it should be data that remains valid after the
AEGP finishes executing.
AEGP finishes it's thing and exits.
effect is now executing.
effect finishes the call, exits, and AE is executing.
at this point, seq/global data handles are no longer valid. (at least you
can't rely on that)
also, anything allocated in the effect's calling function as a local
variable, is no longer valid.
so now your AEGP gets called on idle time.
it should only rely on memory that has kept since the effect was executing.
what memory is kept?
anything in global scope of the AEGP, or pointers to memory that was not
deallocated or moved.
seq data handle may not have been deallocated, but you can't tell if it
moved or not. so you can't rely on it.
if the seq data has another pointer in it, which point to a non movable
piece of data, then you can rely on that pointer.
seq/global handles are locked an unlocked by AE. memory handles are managed
by the plug-in (so you know if they can be relied on or not).
2. AEGP calls effect.
AE is calling the AEGP on idle time.
AEGP is executing.
AEGP calls effect with data.
effect is now executing.
effect uses data gotten from AEGP.
effect optionally returns data to AEGP.
effect exits.
AEGP is now back executing.
AEGP uses data returned from effect. that data can't be references to local
variables in the effect as they are no longer valid.
AEGP exits, AE is now executing.
so in both directions you need to see that at the time the data is used,
that is is valid.
as for sequence data vs arb param.
yes, there is a difference besides undo/redo.
AE creates (multiple) copies of the data stored in arb params before each
call to the plug-in and also after.
if you're storing very large amounts of data in the arb param, then the
copy operations will start dragging your performance down.
it's usually a non-issue, but... it's a point to think about.

What is the best laptop for architectural design?

I mostly need if for revit. I currently have a lenovo thinkpad T61. It has been great but is getting old, and I think it is about to crap out. I would like to stay with lenovo but im up for any suggestions.

Hello,
It might be best to look at the requirements for the architectural design software that you want to run, and then look at which systems match those specifications.
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество

Is MVC2 a design pattern or architecture? for yes and no why?

I am using JSF which follows MVC2. Is MVC2 a design pattern or architecture? For yes and no why? what is the difference between design pattern or architecture?

Hi There,
Maybe this will help answer your questions...
Firstly, MVC2 is a proprietary name for the Microsoft .NET framework based around the Model-View-Controller pattern - it is an updated version of their first attempt - MVC.
The Model-View-Controller pattern harks back to the days of SmallTalk, and as far as I am aware is not included in the original Gang Of Four design patterns, although there is no reason why it can't be considered a design pattern.
Software architecture is about how different parts of the system fit (interface) together and how they relate, including static relationships (cardinality relationships, state) and processes (what happens when), it most often consists of many design patterns each used to address the various needs of a complete system.
Hope this helps
Rich

Architectural/design documentation required for Self Service Expenses application

I'm looking for architectural/design documentation on the Oracle Applications Self Service Expense Reporting application.
Specifically I'd like to know how it was designed & architected, what technologies were used to develop it (e.g. CABO, B24J, Oracle Workflow, AQ etc.) and how these technologies interact to form the final system.
We have a product called the Oracle Migration Workbench. It is a standalone java-based application that facilitates the migration of non-Oracle databases over to Oracle9i. We're investigating the possibility of developing a web-based migration capability. Of course we appreciate that moving from a tool-based, single user solution to a web based, multi user solution is not a trivial task.
Seeing that you guys would have already tackled many of the challenges we face I'd appreciate it if you can provide me with any pertinent information.
Any white papers/architectural collateral you can give me would be greatly appreciated.
thanks in advance
- Garry

Hi Did you ever get this documentation? I would really appreciate some more info on this to [email protected]

A Leading 3D Architecture Designing Services Provider in India.

Hi all!!! This is on behalf of Yantram – A Leading 3D Architecture Designing Services Provider in India.
I am new to this forum and hope to get good support from all the forum members.
Edited by: user10387861 on Oct 3, 2008 2:26 PM

This forum is for oracle users to share their knowledge . Not to support or give service . For support hire a DBA or connect to metalink.
Regards,
Kumar
[www.idatamax.com]

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

Solution Architecture diagram for a SP 2010 intranet portal

hi,
Can any one plz provide a solution architecture diagram for a SP 2010 intranet portal.
want to use news , events, doc libs, Custom WPs, timer jobs, info.mgmnt policies,discussion forum.
So how the diagram would be.
also want to know whats the difference between logical arch.dgrm and soln. arch.dgrm
Are these two same?
any links/sources are highly appreciated.

Hi,
Pls have you check this link :
http://www.astaticstate.com/2010/06/sharepoint-2010-architecture-and-design.html
http://blogs.technet.com/b/seanearp/archive/2010/07/09/technical-diagrams-for-sharepoint-2010.aspx
http://sharepointmagazine.net/articles/best-practices-of-sharepoint-farm-configuring-and-deployment-part-1-architectural-and-logical-planning
Book:
http://www.scribd.com/doc/86735719/SharePoint-2010-Enterprise-Architect-s-Guidebook
Logical architecture:
The Logical Architecture is a definition (usually in the form of a diagram) of how your Portal is built, including hardware, software, services and other integrated components. If it is required to make the “system” work, it belongs in this diagram.
Your diagram should reflect how each component of the system “fits in”, and is connected with, each of the other components. This map isn’t focused on “technology” or how it’s implemented. Rather, it’s focused on how things “logically”
fit together to make up the whole solution.
Solution Architects:
Solution Architects use the Logical and Physical architecture diagrams to effectively plan out their solution and make sure that everything is accounted for and has been thought through before they begin building the solution.
thx
iffi

Architecture/Design Question with best practices ?

Architecture/Design Question with best practices ?
Should I have separate webserver, weblogic for application and for IAM ?
If yes than how this both will communicate, for example should I have webgate at both the server which will communicate each other?
Any reference which help in deciding how to design and if I have separate weblogic one for application and one for IAM than how session management will occur etc
How is general design happens in IAM Project ?
Help Appreciated.

The standard answer: it depends!
From a technical point of view, it sounds better to use the same "midleware infrastructure", BUT then the challenge is to find the lastest weblogic version that is certified by both the IAM applications and the enterprise applications. This will pull down the version of weblogic, since the IAM application stack is certified with older version of weblogic.
From a security point of view (access, availability): do you have the same security policy for the enterprise applications and the IAM applications (component of your security architecture)?
From a organisation point of view: who is the owner of weblogic, enterprise applications and IAM applications. In one of my customer, application and infrastructure/security are in to different departments. Having a common weblogic domain didn't feet in the organization.
My short answer would be: keep it separated, this will save you a lot of technical and political challenges.
Didier.

Architecture Design for CORBA

Similar Messages

Maybe you are looking for