Unable to Import Essbase Metadata in OBIEE 11G (11.1.1.9) using SampleAppV506 VM - Network error [10

Tinotarantino-Oracle

I'm running OBIEE 11.1.1.9 SampleAppV506 VM (VirtualBox  4.3.30) hosted on my Window 7 laptop (32GB / 8 Cores /  1TB SSD).    

An integrated Essbase Server is part of the image and this integrated Essbase Server is listening on port 9799 (I assume this is the default port used by the OBIEE install).

SampleAppV506 VM OBIEE repository has pre-built dashboard content designed to work with the integrated Essbase Server.   

I don't have any problems accessing and using the pre-built OBIEE11g repository content for Essbase that comes with SampleAppV506.  It all works great!!!

However, I am unable to import Essbase Metadata from the integrated Essbase Server using the BI Admin tool.  From BI Admin tool I run

File->Import Metadata.    I provide the Essbase Server and port  (192.168.56.1:9799) and sign-on credentials (weblogic/Admin123).

I'm able to see all of the Essbase Applications on SampleAppv506 VM.  However, when I attempt to import an Essbase database, I get the following error:

Essbase Error 1042006: Network error [10061]:  Failed to connect to [192.168.56.1:9799].      My VirtualBox VM is configured to use NAT

with port forwarding and this is working perfectly for accessing the OBIEE 11g SampleAppv506 content from my browser,  NAT addressing is also working

for SQL Developer client,  Essbase Client, BI Administration Tool, etc.

I've installed 11.1.2.4 Essbase client to my host machine (as documented in the OBIEE 11g Administration Guide and (Doc ID 2006521.1).

I can connect using ESSCMD to the integrated Essbase Server on the  SampleAppv506 VM.    I can run EAS console to connect to the integrated Essbase Server.

About the only thing I can't do is Import Essbase Metdata.

Any help would be greatly appreciated. 

Tinotarantino-Oracle

I've have a update to my original post that may shed some light on the underlying problem.      In addition to the standard SampleAppv506 VM, I've also installed the standalone EPM 11.1.2.4 plug-in for SampleAppv506.

When I  only startup the standard OBIEE11g server with integrated Essbase, I  AM ABLE TO SUCCESSFULLY IMPORT ESSBASE METADATA using the BI Admin tool.   However, when I then

startup the standalone EPM 11.1.2.4 instance (which is running n a separate WLS domain from OBIEE) on the same SampleAppV506 VM,, I get the error that I mentioned in my original post.       The standalone Essbase server however is

listening on the default port (1423), so there should be no conflict here?         Has anyone  tried this configuration and been successful at importing Essbase metadata when both OBIEE11g is running (with integrated Essbase server)

and the EPM 11.1.2.4 standalone plug-iin instance running at the same time in SampleAppv506?   

Tinotarantino-Oracle

Issue solved.   As it turns out, my problem seems to have been related to my use of NAT networking on my SampleApp506 VM.   NAT requires you to use port-forwarding for every port you need access to on the guest VM so I may have missed something here?.   In any case,  after switching to BRIDGED networking on my VM,   I could successfully use the BI Admin tool to import ESSBASE metadata from the integrated EPM 11.1.2.4  and standalone EPM 11.1.2.4 plug-in of the SampleAppv506 VM.   In addition, I also successfully imported Hyperoin planning metadata using the new ADM driver in OBIEE 11.1.1.9.