Thanks for the reply. I’ll try to fill in the blanks and see if it helps:
Are you using security?
Yes, EntireX security would be used.
If yes, is the same userid used for all/most calls are do they differ from call to call?
Yes, I’m talking about one user’s session.
Are you calling the same wrapper object or different ones?
I would assume that different wrappers would be used depending on the functions the user executes.
Is your Broker configured with AUTOLOGON=YES or =NO?
Currently, it is set to AUTOLOGON=NO, I think. It’s set to the default, and I assume that would be NO.
It also depends where you want to achieve an optimization:
Do you want to reduce the number of Broker calls ?
I’m not sure. We just don’t want to “carry around” the user’s id and password throughout the user’s session. We want to log on once to authenticate and not have to pass the user’s credentials (user id and password) to Broker every single time we call it.
Do you want to optimize the performance of the Java application?
That would be nice.
Do you want to reduce the overhead of user authentication?
I don’t think it’s the overhead we’re concerned with. We just don’t want to constantly be passing the user’s credentials around.
Do you want to reduce the number of client sessions (NUM-CLIENT) in the Broker?
I don’t know, do I? I’m VERY new to this and haven’t looked into optimization strategies.
Does that help clarify things at all?
I guess I’m wondering what my options are, such as keeping a ‘logged on’ broker object in Session, and trying to find coding samples. I just don’t know all the ways available to manage these EntireX objects over the life of a user’s Session. Maybe I’m trying to do something that nobody else does or trying to avoid doing something that everybody else does do. Huh? Anyway, any suggestions would be greatly appreciated.