cancel
Showing results for 
Search instead for 
Did you mean: 

Where should we develop WAD Applications

Former Member
0 Kudos

Hello all,

I must admit that by nature I am strictly an EP person, but I am desperately looking for information regarding BI.

Currently in our company:

1. Most queries are developed only in production. What are the risks of doing this? How does this effect using the WAD?

2. We are currently sharing the EP java stack with BI. What risks are here in relationshipt to WAD?

3. What information is written by WAD to the java stack? is there a hight risk for causing performance issues, bringing down the system, etc? And to mitigate these is the best practice to Develop only in Dev and transport?

Overall what is the best way to proceed with development of BI, best way to maintain change procedures, and make sure the users are only seeing the best product for them?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Either way by developing it in Dev or Production dosent make a difference. The negitive side is that you would create a large query that takes a lot of time and resources in production. It is safer to test it in Dev for performance and correctness and then get it transported. Coming to the question on WAD, if the query is too large it will take up memory and effect the Java Stack and potentially slow down the system with a OUT OF MEMORY error.

Answers (0)