General Design Questions

Hello,
I am developing a web application and could use some architectural advice. I've done lots of reading already, but could use some direction from those who have more experience in multi-tier development and administration than I. You'll find my proposed solution listed below and then I have some questions at the bottom. I think my architecture is fairly standard and simple to understand--I probably wrote more than necessary for you to understand it. I'd really appreciate some feedback and practical insights. Here is a description of the system:
Presentation Layer
So far, the presentation tier consists of an Apache Tomcat Server to run Servlets and generate one HTML page. The HTML page contains an embedded MDI style Applet with inner frames, etc.; hence, the solution is Applet-centric rather than HTML-centric. The low volume of HTML is why I decided against JSPs for now.
Business Tier
I am planning to use the J2EE 1.4 Application Server that is included with the J2EE distribution. All database transactions would be handled by Entity Beans and for computations I'll use Session Beans. The most resource intensive computational process will be a linear optimization program that can compute large matrices.
Enterprise Tier
I?ll probably use MySql, although we have an Oracle 8 database at our disposal. Disadvantage of MySql is that it won't have triggers until next release, but maybe I can find a work-around for now. Advantage is that an eventual migration to Linux will be easier on the wallet.
Additional Information
We plan to use the system within our company at first, with probably about 5 or less simultaneous users. Our field engineer will also have access from his laptop. That means he'll download the Applet-embedded HTML page from our server via the Internet. Once loaded, all navigation will be Applet-centered. Data transfer from the Applet to Servlet will be via standard HTTP.
Eventually we would like to give access of our system to a client firm. In other words, we would be acting as an application service provider and they would access our application via the Internet. The Applet-embedded HTML page would load onto their system. The volume would be low--5 simultaneous users max. All users are well-defined in advance. Again, low volume HTML generation--Applet-centric.
My Questions
1). Is the J2EE 1.4 Application Server a good production solution for the conditions that I described above? Or is it better to invest in a commercial product like Sun Java System Application Server 7 ? Or should I forget the application server concept completely?
2). If I use the J2EE Application Server, is this a good platform for running computational programs (via Session Beans)? Or is it too slow for that? How would it compare with using a standalone Java application--perhaps accessed from the Servlet via RMI? I guess using JNI with C++ in a standalone application would be the fastest, though a bit more complex to develop. I know it is a difficult question, but what is the most practical solution that strikes a balance between ease-of-programming and speed?
3). Can the J2EE 1.4 Application Server be used for running the presentation tier (Servlets and HTML) internally on our intranet? According to my testing, it seems to work, but is it a practical solution to use it this way?
4). I am running Tomcat between our inner and outer firewalls. The database would of course be completely inside both firewalls. Should the J2EE (or other) Application Server also be in the so-called 'dmz' with Tomcat? Should it be on the same physical server machine as Tomcat?
5). Can Tomcat be used externally without the Apache Web Server? Remember, our solution is based on Servlets and a single Applet-embedded HTML page, so high volume HTML generation isn't necessary. Are there any pros/cons or security issues with running a standalone Tomcat?
So far I've got Tomcat and the J2EE Application Server running and have tested my small Servlet /Applet test solution on both. Both servers work fine, although I haven't tested any Enterprise Beans on the application server yet. I'd really appreciate if anyone more experienced than I can comment on my design, answer some of my questions, and/or give me some advice or insights before I start full-scale development. Thanks for your help,
Regards,
Itchy

I can give my opinion on some of these questions and a resource for the others.
<question>
1). Is the J2EE 1.4 Application Server a good production solution for the conditions that I described
Or is it better to invest in a commercial product like Sun Java System Application Server 7 ? Or should I forget the application server concept completely?
</question>
Yes, the J2EE 1.4 app server is a good solution for these conditions. Specifically, I would use SJSAS PE 8.0 version or the J2EE SDK. They are free version that will meet your needs. You get the latest J2EE 1.4 platform features. As your needs grow you can transition to an enterprise version of the appserver (SE/EE). If you choose to go commercial please note that SJSAS 7.0 is a J2EE 1.3 platform.
<question>
2). If I use the J2EE Application Server, is this a good platform for running computational programs (via Session Beans)? Or is it too slow for that? How would it compare with using a standalone Java application--perhaps accessed from the Servlet via RMI? I guess using JNI with C++ in a standalone application would be the fastest, though a bit more complex to develop. I know it is a difficult question, but
what is the most practical solution that strikes a balance between ease-of-programming and speed?
</question>
I guess you will not know for sure unless you perform some bench mark tests. But my opinion is the ease of development features you gain by using an app server far out weigh any performance increases you may get using a native soluton. Also, it is not clear that a native solution would actually be faster, with the latest JIT compilers Java performance is comparable to C++, your milage may vary depending on your application.
<question>
3). Can the J2EE 1.4 Application Server be used for running the presentation tier (Servlets and HTML) internally on our intranet? According to my testing, it seems to work, but is it a practical solution to use it this way?
</question>
Yes I would use the app server for both your presentation tier and business tier.
As for the other issues you may want to look at the Java Enterprise Blue Prints located at: http://java.sun.com/j2ee/1.4/download.html#blueprints

Similar Messages

A general design question using servlets

Hello all,
          We have 2 WebLogic app./web servers. Lets call the first one Server A and
          the other Server B. Server A shows a web page to the client/browser and that
          has links to Server B. Now there is some authentication information that
          needs to be passed to Server B too. We were thinking of embedding that
          information in the web page itself. So a link on a page served by Server A
          could look like:
          Login to Server B
          Now the issue with such a solution is that the login token is exposed to the
          browser and the client. This would lead to the token being copied and pasted
          for replay attacks on Server B. I was thinking of better ways to solve this
          issue. PLease let me know if you have faced such issues earlier and a better
          solution using Servlets/JSP etc..
          Thanks.


          Either use a cookie by setting its domain name your two servers share, or add very
          short timeout. In later case, you generate the token with very short timeout in
          one server, use redirect to send the request to the second server, then use the
          session objects in both servers to indicate the user login. When you logout, you
          need kill the session objects on both servers.
          "Gaurav Khanna" <[email protected]> wrote:
          >Hello all,
          >
          >We have 2 WebLogic app./web servers. Lets call the first one Server A
          >and
          >the other Server B. Server A shows a web page to the client/browser and
          >that
          >has links to Server B. Now there is some authentication information that
          >needs to be passed to Server B too. We were thinking of embedding that
          >information in the web page itself. So a link on a page served by Server
          >A
          >could look like:
          >Login to Server
          >B
          >
          >Now the issue with such a solution is that the login token is exposed
          >to the
          >browser and the client. This would lead to the token being copied and
          >pasted
          >for replay attacks on Server B. I was thinking of better ways to solve
          >this
          >issue. PLease let me know if you have faced such issues earlier and a
          >better
          >solution using Servlets/JSP etc..
          >
          >
          >Thanks.
          >
          >

Design question: methods returning objects

I have a general design question. When, in general (and why), should you have a method alter an object via it's methods but not return the object as opposed to doing the same operation in a method and then return it.
Consider the two below methods which do basically the same thing. When is one desireable over the other, and why?
Cheers--
public void setMyIntField(SomeObject pObj){
pObj.setSomeInt(5);
public SomeObject setMyIntField(SomeObject pObj){
pObj.setSomeInt(5);
return pObj;
}

Let me give a better example:
class FruitWorker{
private void someMethod(){
    HashMap myCitrus = new HashMap();
    HashMap myTropicals = new Hashmap();
    // use my no return obj method
    addFruitProps1(myCitrus,
                   "tartnes",
                   new FruitProperty("very!" ));
    // use my return object method
    myTropicals = addFruitProps2(myCitrus,
                                  "sweetness",
                                   new FruitProperty("little bit" ));
}// end method
private void addFruitProperties1(HashMap pFruitProps,
                                   String pProp
                                   FruitProperty pVal){
    pFruitProps.add( pProp,pVal);
}// end method
private HashMap addFruitProperties2(HashMap pFruitProps,
                                   String pProp
                                   FruitProperty pVal){
    pFruitProps.add( pProp,pVal);
    return pFruitProps;
}// end method
}// end class

Design question about when to use inner classes for models

This is a general design question about when to use inner classes or separate classes when dealing with table models and such. Typically I'd want to have everything related to a table within one classes, but looking at some tutorials that teach how to add a button to a table I'm finding that you have to implement quite a sophisticated tablemodel which, if nothing else, is somewhat unweildy to put as an inner class.
The tutorial I'm following in particular is this one:
http://www.devx.com/getHelpOn/10MinuteSolution/20425
I was just wondering if somebody can give me their personal opinion as to when they would place that abstracttablemodel into a separate class and when they would just have it as an inner class. I guess re-usability is one consideration, but just wanted to get some good design suggestions.

It's funny that you mention that because I was comparing how the example I linked to above creates a usable button in the table and how you implemented it in another thread where you used a ButtonColumn object. I was trying to compare both implementations, but being a newbie at this, they seemed entirely different from each other. The way I understand it with the example above is that it creates a TableRenderer which should be able to render any component object, then it sets the defaultRenderer to the default and JButton.Class' renderer to that custom renderer. I don't totally understand your design in the thread
http://forum.java.sun.com/thread.jspa?forumID=57&threadID=680674
quite yet, but it's implemented in quite a bit different way. Like I was saying the buttonClass that you created seem to be creating an object of which function I don't quite see. It looks more like a method, but I'm still trying to see how you did it, since it obviously worked.
Man adding a button to a table is much more difficult than I imagined.
Message was edited by:
deadseasquirrels

Design question: Scheduling a Variable-timeslot Resource

I originally posted this in general java programming, because this seemed like a more high-level design descussion. But now I see some class design questions. Please excuse me if this thread does not belong here (this is my first time using the forum, save answering a couple questions).
Forum,
I am having trouble determining a data structure and applicable algorithm (actually, even more general than the data structure -- the general design to use) for holding a modifiable (but more heavily read/queried than updated), variable-timeslot schedule for a given resource. Here's the situation:
Let's, for explanation purposes, say we're scheduling a school. The school has many resources. A resource is anything that can be reserved for a given event: classroom, gym, basketball, teacher, janitor, etc.
Ok, so maybe the school deal isn't the best example. Let's assume, for the sake of explanation, that classes can be any amount of time in length: 50 minutes, 127 minutes, 4 hours, 3 seconds, etc.
Now, the school has a base operation schedule, e.g. they're open from 8am to 5pm MTWRF and 10am to 2pm on saturday and sunday. Events in the school can only occur during these times, obviously.
Then, each resource has its own base operation schedule, e.g. the gym is open from noon to 5pm MTWRF and noon to 2pm on sat. and sun. The default base operation schedule for any resource is the school which "owns" the resource.
But then there are exceptions to the base operation schedule. The school (and therefore all its resources) are closed on holidays. The gym is closed on the third friday of every month for maintenance, or something like that. There are also exceptions to the available schedule due to reservations. I've implemented reservations as exceptions with a different status code to simplify things a little bit: because the basic idea is that an exception is either an addition to or removal from the scheduleable times of that resource. Each exception (reservation, closed for maintenance, etc) can be an (effectively) unrestricted amount of time.
Ok, enough set up. Somehow I need to be able to "flatten" all this information into a schedule that I can display to the user, query against, and update.
The issue is complicated more by recurring events, but I think I have that handled already and can make a recurring event be transparent from the application point of view. I just need to figure out how to represent this.
This is my current idea, and I don't like it at all:
A TimeSlot object, holding a beginning date and ending date. A data structure that holds list of TimeSlot objects in order by date. I'd probably also hold an index of some sort that maps some constant span of time to a general area in the data structure where times around there can be found, so I avoid O(n) time searching for a given time to find whether or not it is open.
I don't like this idea, because it requires me to call getBeginningDate() and getEndDate() for every single time slot I search.
Anyone have any ideas?

If I am correct, your requirement is to display a schedule, showing the occupancy of a resource (open/closed/used/free and other kind of information) on a time line.
I do not say that your design is incorrect. What I state below is strictly my views and should be treated that way.
I would not go by time-slot, instead, I would go by resource, for instance the gym, the class rooms (identified accordingly), the swimming pool etc. are all resources. Therefore (for the requirements you have specified), I would create a class, lets say "Resource" to represent all the resources. I would recommend two attributes at this stage ("name" & "identifier").
The primary attribute of interest in this case would be a date (starting at 00:00hrs and ending at 24:00hrs.), a span of 24hrs broken to the smallest unit of a minute (seconds really are not very practical here).
I would next encapsulate the availability factor, which represents the concept of availability in a class, for instance "AvailabilityStatus". The recommended attributes would be "date" and "status".
You have mentioned different status, for instance, available, booked, closed, under-maintainance etc. Each of these is a category. Let us say, numbered from 0 to n (where n<128).
The "date" attribute could be a java.util.Date object, representing a date. The "status", is byte array of 1440 elements (one element for each minute of the day). Each element of the byte array is populated by the number designation of the status (i.e, 0,1,2...n etc.), where the numbers represent the status of the minute.
The "Resource" class would carry an attribute of "resourceStatus", an ordered vector of "ResourceStatus" objects.
The object (all the objects) could be populated manually at any time, or the entire process could be automated (that is a separate area).
The problem of representation is over. You could add any number of resources as well as any number of status categories.
This is a simple solution, I do not address the issues of querying this information and rendering the actual schedule, which I believe is straight forward enough.
It is recognized that there are scope for optimizations/design rationalization here, however, this is a simple and effective enough solution.
regards
[email protected]

A general OOP question

Hi
I have a general OOP design question, and am wondering if someone could relate an answer to the following design?
I have a class called MediaFolderImport(); - it's designed to build a window with various editing tools in it.
Within it's constructor, I'm calling a bunch of functions to build the window...
   createTitle();
   createInstructions();
   createToolPanel();
   createDataGrid ();
   createOpen();
   createSave();
In my document class, I instantiate it...
public var File_Folder_Import:MediaFolderImport=new MediaFolderImport();
and then...
addChild(File_Folder_Import);
Voila! - the window appears. I WAS very proud of myself.
Now I want to access something inside the window. Specifically, there's a radio button that was created in createToolPanel(); - I want to update it to be selected or not selected when I receieve the user's preference from an xml settings file at start up (xml is loaded into the doc class).
General question:
What is the best practice, smart way to have designed this?
- call createToolPanel(); from the doc class instead of within MediaFolderImport();, and somehow (magically) have access to the radio button?
- leave the design as is, but add some sort of listener within MediaFolderImport that listens for changes to the xml in the doc class, and updates accordingly?
- do it the way I'm trying to, ie try to access the radio button directly from the doc class (which isn't working):
File_Folder_Import.myRadioButton.selected = true;
- a better way someone can briefly explain the concept of?
Another way to explain my design is...
- a bunch of different windows, each created by a different class
- xml file loads preferences, which need to be applied to different tools (radio buttons, check boxes, text fields etc) in the different windows
I read a lot of posts that talk about how public vars are mostly bad practice. So if you are making your class vars private, what is the best way to do the kind of inter-class communicating I'm talking about here?
I think someone throwing light on this will help me solidify my understanding of OOP.
Thank you for your time and help.

You're already very used to using properties for the built-in AS classes and that's the best practice means of configuring your class. It's a "state" that you want to simply expose. The get/set method moccamaximum mentioned is the ideal route.
The main reason you want to use get/set functions is validation. You want your class to act properly if you send an invalid value. Especially if anyone else besides yourself is going to use the class. Plan for the worst.
The general concept is, make a private variable for any 'state' you want to remember using an underscore in the variable name to easily identify it as a private var, then make get/set functions with the same name with any required validation without the underscore.
e.g.
package
     public class MyClass
          // property called 'mode' to track something with an int
           private var _mode:int = 0;
          public function MyClass() {} // empty constructor
          // get (type enforced)
          public function get mode():int { return mode; }
          // set, requiring a value
          public function set isChecked(modeVal:int):void
               // if no value is sent, ignore
               if (!modeVal) { return; }
               _mode = modeVal;
Your validation will go a long way to easily debugging your classes as they grow in size. Eventually they should throw exceptions and errors if they're not valid. Then you will be best practice. Do note that if your validation requires quite a bit of logic it's common to upgrade the property to a public method. get/set should be reserved for simple properties.

General dreamwevaer question

hello dreamweavers.
im a newbie going to use dreamweaver from next week and beyond,so id like to ask the following:
should i design the website in photoshop and then import it into dreamwevaer,in order to code it?
is dreamwevaer flexible in design point of view,or is it mostly getting finished designs such as headers,footers,flash banners,
and then building up the site where things so and such.
thank you.

Hello Nancy.
seems like an informative website,i can see it is easy to understand the
basics.
Στις 23 Μαρτίου 2012 4:29 π.μ., ο χρήστης Nancy O. <[email protected]>έγραψε:
Re: general dreamwevaer question created by Nancy O.<http://forums.adobe.com/people/Nancy+O.>in
Dreamweaver - View the full discussion<http://forums.adobe.com/message/4283588#4283588

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.

Design questions on using JMX

I have been reading about JMX and trying to understand it
I have some specific design realted questions and wanted some opinions to validate my understanding
Assume a simple j2ee application that exposes 2 webservices .
I would like to find out how many times each service is called and the total number of success/faults/errors
encountered for each service along with params like starttime etc
From what I have understood , I will have to first create a Bean , say "StatsCollector"
and then creae a StatsCollectorMBean interface.
The StatsCollector will provide the methods to set/update the above values and those will also be exposed by the StatsCollectorMBean interface
1) I have trouble understanding how to create and maintain the MBean Resource...
Shouldnt there be always 1 instance of this resource ? ie shouldnt there be only one StatsCollector ?
Most of the examples create a simple class "Hello implements HelloMBean" and that makes it a MBean
but they create Hello hello = new Hello() and then register it with the MBean server
What if we create multiple objects of Hello? Wouldnt that defeat the porpose of the MBean ?
I think that we need to make sure that this resource is always created once only.
Is that correct ?
2) Is it the right practice to separate your MBean and your "managed" resource ?
ie in the above case , should there be a Singleton StatsCollector POJO that stores the Appliction
statistics and another StatsMBean that will be the MBean that will access the POJO ? This makes sure that your Resource does not have
dependency management classes.
3) How does the application update the values in the MBean ?
In the above example , how do you update the success and failure counts in the MBean from the application ?
Can I update the singleton StatsCollector directly or do I have to go through the MBean Server to update
any value in the MBean ?
If I update them directly , will they be "visible" thru the MBean server ?
4) Assuming that the above app gets deployed in a appserver like WebSphere and in a Clustered environment ,
how to ensure that statisitcs are collected for all the services on all servers cummulativly ?
Is this something that the appserver should provide ? Do we register the MBean with the Appserver
MBean server ?
Any ideas/suggestions will be helpful !
thanks
Pat

Hello pat,
very interesting questions. You are covering the main JMX design questions there.
You should have a look (if you not already did) to the JMX best practices : http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/best-practices.jsp
This document summarize common JMX design patterns.
Answers to your questions:
1) The resources you want to manage/monitor are Web Services. The life cycle of these services is handled by the J2EE container itself. As you say, the tricky part is to link the WebService resource life cycle to the MBean resource
The MBean leaves inside its own container, the MBeanServer.
You should identify an initialization phase in which you create your MBeans and register them inside the MBeanServer once.
In your case, you can go for a single collector that monitors the 2 Web Services or a collector per Web Service. It seems that you want to track each service independently. Having 2 MBeans should offer a more flexible solution.
If you go for 1 MBean, you should name it "<your management domain>:type=StatsCollector". This name identify an MBean for which you have a single instance. Once the collector registered with this name, the MBeanServer will guarantee that no MBean with the same name can be registered.
If you go for 2 MBeans, you should add the Web Service name to each MBean ObjectName. For example:
MBean 1 : "<your management domain>:type=StatsCollector,name=MyWebService1"
MBean 2 : "<your management domain>:type=StatsCollector,name=MyWebService2"
Example of MBean creation and registration code :
StatsCollector collector1 = new StatsCollector();
ManagementFactory.getPlatformMBeanServer().registerMBean(collector1,
new ObjectName("com.foo.bar:type=StatsCollector,name=WebService1");
At this point you have an MBean registered inside the platform MBeanServer.
2) A Standard MBean is formed of a java interface and a class. Generally the interface and the class are not separated. They could be but I don't see a strong reason in your case to have the POJO and interface not being the same object.
3) You shouldn't expose the methods to set the values in your MBean interface. Only getters should be visible. It means that you will have to keep a direct reference to the collectors to update the statistics. During your initialization phase, you could use JNDI to register the collector instances. The WebServices will then use JNDI to retrieve the collectors.
An example of a simplified StatsCollector class and StatsCollectorMBean interface
public interface StatsCollectorMBean {
public int getNumRequests();
public class StatsCollector implements StatsCollectorMBean {
private int numRequests.
public int getNumRequests() {
return average;
public serviceCalled() {
numRequests++;
In the above example, serviceCalled is not part of the management interface and is called by the Web Service.
4) Difficult question for which I can't provide you with a reply. JMX doesn't offer such cumulative service in a standard way. In some appserver (glassfish for instance), MBeans are cascaded inside the domain server. There is no cumulative representation offered, but you could implement your own by defining new MBeans linked to the StatsCollector ones.
To conclude, Appservers are offering some "out of the box" management and monitoring features . For example glassfish relies on the AMX framework (that is JMX based) . AMX (https://glassfish.dev.java.net/javaee5/amx/) allows you to monitor and manage your services. A possible solution would be to rely on this infrastructure to build your own management and monitoring.
Hope this help.
Regards.
Jean-Francois Denise

LDAP design question for multiple sites

LDAP design question for multiple sites
I'm planning to implement the Sun Java System Directory Server 5.2 2005Q1 for replacing the NIS.
Currently we have 3 sites with different NIS domains.
Since the NFS over the WAN connection is very unreliable, I would like to implement as follows:
1. 3 LDAP servers + replica for each sites.
2. Single username and password for every end user cross those 3 sites.
3. Different auto_master, auto_home and auto_local maps for three sites. So when user login to different site, the password is the same but the home directory is different (local).
So the questions are
1. Should I need to have 3 domains for LDAP?
2. If yes for question 1, then how can I keep the username password sync for three domains? If no for question 1, then what is the DIT (Directory Infrastructure Tree) or directory structure I should use?
3. How to make auto map work on LDAP as well as mount local home directory?
I really appreciate that some LDAP experta can light me up on this project.

Thanks for your information.
My current environment has 3 sites with 3 different NIS domainname: SiteA: A.com, SiteB:B.A.com, SiteC:C.A.com (A.com is our company domainname).
So everytime I add a new user account and I need to create on three NIS domains separately. Also, the password is out of sync if user change the password on one site.
I would like to migrate NIS to LDAP.
I want to have single username and password for each user on 3 sites. However, the home directory is on local NFS filer.
Say for userA, his home directory is /user/userA in passwd file/map. On location X, his home directory will mount FilerX:/vol/user/userA,
On location Y, userA's home directory will mount FilerY:/vol/user/userA.
So the mount drive is determined by auto_user map in NIS.
In other words, there will be 3 different auto_user maps in 3 different LDAP servers.
So userA login hostX in location X will mount home directory on local FilerX, and login hostY in location Y will mount home directory on local FilerY.
But the username and password will be the same on three sites.
That'd my goal.
Some LDAP expert suggest me the MMR (Multiple-Master-Replication). But I still no quite sure how to do MMR.
It would be appreciated if some LDAP guru can give me some guideline at start point.
Best wishes

Design question for database connection in multithreaded socket-server

Dear community,
I am programming a multithreaded socket server. The server creates a new thread for each connection.
The threads and several objects witch are instanced by each thread have to access database-connectivity. Therefore I implemented factory class which administer database connection in a pool. At this point I have a design question.
How should I access the connections from the threads? There are two options:
a) Should I implement in my server class a new method like "getDatabaseConnection" which calls the factory class and returns a pooled connection to the database? In this case each object has to know the server-object and have to call this method in order to get a database connection. That could become very complex as I have to safe a instance of the server object in each object ...
b) Should I develop a static method in my factory class so that each thread could get a database connection by calling the static method of the factory?
Thank you very much for your answer!
Kind regards,
Dak
Message was edited by:
dakger

So your suggestion is to use a static method from a
central class. But those static-methods are not realy
object oriented, are they?There's only one static method, and that's getInstance
If I use singleton pattern, I only create one
instance of the database pooling class in order to
cionfigure it (driver, access data to database and so
on). The threads use than a static method of this
class to get database connection?They use a static method to get the pool instance, getConnection is not static.
Kaj

SOA real-time design question

Hi All,
We are currently working with SOA Suite 11.1.1.4. I have a SOA application requirement to receive real-time feed for six data tables from an external third party. The implementation consists of five one-way operations in the WSDL to populate the six database tables.
I have a design question. The organization plans to use this data across various departments which requires to replicate or supply the data to other internal databases.
In my understanding there are two options
1) Within the SOA application fork the data hitting the web-service to different databases.
My concern with this approach is what if organizations keep coming with such requests and I keep forking and supplying multiple internal databases with the same data. This feed has to be real-time, too much forking with impact the performance and create unwanted dependencies for this critical link for data supply.2) I could tell other internal projects to get the data from the populated main database.
My concern here is that firstly the data is pushed into this database flat without any constraints and it is difficult to query to get specific data. This design has been purposely put in place to facilitate real-time performance.Also asking every internal projects to get data from main database will affect its performance.
Please suggest which approach should I take (advantage/disadvantage. Apart from the above two solutions, is there any other recommended solution to mitigate the risks. This link between our organization and external party is somewhat like a lifeline for BAU, so certainly don't want to create more dependencies and overhead.
Thanks

I had tried implementing the JMS publisher/subscriber pattern before, unfortunately I experienced performance was not so good compared to the directly writing to the db adapter. I feel the organization SOA infrastructure is not setup correctly to cope with the number of messages coming through from external third party. Our current setup consists of three WebLogic Servers (Admin, SOA, BAM) all running on only 8GB physical RAM on one machine. Is there Oracle guideline for setting up infrastructure for a SOA application receiving roughly 600000 messages a day. I am using SOA 11.1.1.4. JMS publisher/subscriber pattern just does not cope and I see significant performance lag after few hours of running. The JMS server used was WebLogic JMS
Thanks
Edited by: user5108636 on Jun 13, 2011 4:19 PM
Edited by: user5108636 on Jun 13, 2011 7:03 PM

Workflow design questions: FM vs WF to call FM

Hereu2019s a couple of workflow design questions.
1. We have Workitem 123 that allow user to navigate to a custom transaction TX1. User can make changes in TX1. At save or at user command of TX1, the program will call a FM (FM1) to delete WI 123 and create a new WI to send to a different agent.
Since Workitem 123 is still open and lock, the FM1 cannot delete it immediately, it has to use a DO loop to check if the Workitem 123 is dequeued before performing the WI delete.
Alternative: instead of calling the FM1, the program can raise an event which calls a new workflow, which has 1 step/task/new method which call the FM1. Even with this alternative, the Workitem 123 can still be locked when the new workflowu2019s task/method calls the FM1.
I do not like the alternative, which calls the same FM1 indirectly via a new workflow/step/task/method.
2. When an application object changes, the user exit will call a FMx which is related to workflow. The ABAP developer do not want to call the FMx directly, she wants to raise an event which call a workflow .. step .. task .. method .. FMx indirectly. This way any commit that happens in the FMx will not affect the application objectu2019s COMMIT.
My recommendation is to call the FMx using u2018in Update tasku2019 so that the FMx is only called after the COMMIT of the application object.
Any recommendation?
Amy

Mike,
Yes, in my first design, the TX can 1. raise a terminating event for the existing workitem/workflow and then 2. raise another event to call another workflow. Both 1 and 2 will be in FM1.
Then the design question is: Should the FM1 be called from TX directly or should the TX raise an event to call a new workflow which has 1 step/task, which calls a method in the Business object, and the method calls the FM1?
In my second design question, when an application object changes, the user exit will call a FMx which is related to workflow. The ABAP developer do not want to call the FMx directly, she wants to raise an event which call a workflow, which has 1 step/task, which calls a method, which calls the FMx indirectly. This way any commit that happens in the FMx will not affect the application objectu2019s COMMIT.
My recommendation is either call the FMx using u2018in Update tasku2019 so that the FMx is only called after the COMMIT of the application object or raise an event to call a receiver FM (FMx).
Thanks.
Amy

Method design question...and passing object as parameter to webserice

I am new to webservice...one design question
i am writing a webservice to check whether a user is valid user or not. The users are categorized as Member, Admin and Professional. For each user type I have to hit different data source to verify.
I can get this user type as parameter. What is the best approach to define the method?
Having one single method �isValidUser � and all the client web service can always call this method and provide user type or should I define method for each type like isValidMember, isValidAdmin ?
One more thing...in future the requirement may change for professional to have more required field in that case the parameter need to have more attribute. But on client side not much change if I have a single isValidUser method...all they have to do is pass additional values
isValidUser(String username, String usertype, String[] userAttributes){
if usertype == member
call member code
else if usertype = professional
call professional code
else if usertype = admin
call admin code
else
throw error
or
isValidMember(String username, String[] userAttributes){
call member code
One last question, can the parameter be passed as object in web service like USER object.

First of all, here is my code
CREATE OR REPLACE
TYPE USERCONTEXT AS OBJECT
user_login varchar2,
user_id integer,
CONSTRUCTOR FUNCTION USERCONTEXT (
P_LOGIN IN INTEGER
P_ID_ID IN INTEGER
) RETURN SELF AS RESULT
Either your type wont be compiled or this is not the real code..

Aggregation level - design question

Hi, All
we are in BI-IP ( Netweaver 2004s SPS16).
I have a design question for this scenario.
User needs to plan the amounts for a duration (start period and end period), Jan2008 -Dec2008 (001.2008, 012.2008) = 12000.
We need to distribute this to the periods equally. 001.2008 = 1000, 002.2008 =1000 .... 012.2008=1000.
If the user changes the period amounts, it should be reflected back in the duration amount.
Pl suggest the design for the aggregation levels to achieve this.
Thanks in advance.
velu

Hello Velu,
As the name also goes, creating an "aggregation level" will only result in "aggregation". What your requirement is, is called disaggregation or distribution - this cannot happen automatically - you will either have to use the feature in input queries or use the distribution planning function or create your own planning function using fox/exit.

General Design Questions

Similar Messages

Maybe you are looking for