Help Requested - Agents/Scheduler/Bursting Mode/

Question

Hello,
I have OBIEE 11G.
I have an automated email bursting requirement.
The details are -
I have one Table of people's names, address, email id and personal details. These people are not intended to be OBIEE users.
It is a table with people's names and email id.
Using each person's id(Pri key), I want to create a personalized email message and send it out to the intended email.
Sample rows-
Name: Vikram, Address: 123 abc st, Email: [email protected]
Name: Ram, Address: 345 xyz st, Email: [email protected]
message would be
Hello <vikram>
<Addr: 123 abc st>
Welcome!
Thanks
And it has to be sent to the email [email protected]
(( I'm researching more on using the SA system table .. but I really do not want to create them as OBIEE users.))
I want help in terms of what would be the best way to do that. I need direction to look into.
Further action:
Each time a new user is added to the table - the personalized email should be sent to that member. ((Maybe use flags??)
(I was thinking in terms of Triggers - & is there a way to use scripting for scheduling agents? command line?)
Please ask more details and I can answer them for help.
Thanks
Vikram

Answer 1

Hi! Thanks for the reply,
After much googling we've finally found a stable configuration.
java.args=-server -Xmx768m -Xss64k -Dsun.io.useCanonCaches=false -XX:MaxPermSize=512m -XX:+UseParallelGC -Dcoldfusion.rootDir={application.home}/ -verbose:gc -Xloggc:c:/Jrun4/logs/gc/gcInstance1b.log
I tried playing with the survivor ratio but came back to the default when I didn't notice much improvement.  In the end what did it (pretty sure) is -Xss to reduce the requests size living on the stack.  Our large initial heap, perm + overhead combined with the default request size was causing the JVM to go over and blow up I think.
We've been stable for over a month now, the next step for us is to reduce the MaxPermSize a little at a time to find our optimal range.