Re: BEx Query Designer -> Execute pops up blank Internet Explorer session

Looks like I was able to get past this issue. After going through all the steps outlined in the administrators guide & the wiki that JORDAN FRANCO referenced, I did the following:

1. Setup SAP Authentication in the CMC. Authentication Application.
   1. Select SAP
   2. Created logical system connection to SAP BW by specifying appropriate settings.
   3. Imported Roles
   4. User Update: Manually updated all roles & aliases.
2. Linked my Enterprise user to my SAP user in the CMC (Users and Groups).
   1. Select User. Right-click, Properties. Select "Assign Alias", and link the accounts.
3. Enabled Authentication Type selection on BI launch Pad.
   1. Followed steps in BI Platform Administrators guide under section "To configure the BI launch pad logon screen".
   2. NOTE: I had to use WDeploy utility to formally bake in the changes. Others on SCN appear to have gotten by without this step. Fortunately I'm in a POC environment. I would have had more concerns doing so in a productive environment, as the utility repackages the entire BOE environment. I wouldn't do this in a real production landscape without assurances that I have a solid backup in place as it seems a bit risky to me.
4. Logged onto BI Launch Pad with my SAP account credentials using SAP authentication. I was then able to open BEx Web Applications within the launch pad, and also run BEx queries directly in BOE without the need for a Java stack.
5. I then closed my browser session and logged back into BOE using Enterprise authentication, logging on with my personal BOE account that was linked to my SAP account in step 2. I was also able to open web applications in this way as well. The same was true when I ran a query from BEx and logged on initially using enterprise account.
6. I did not enable SSO anywhere, so I always had to logon 2X, which is fine for my use case. I really just want the standard query designer functionality to work. In a production landscape, we'd liklely implement SSO, though I've seen some historical concerns there (which I believe have since been resolved in later SP's).