Portal iView not showing list of tables when creating the iView?

[Former Member]

Hello,

I'm using 5.5 SP6. I have a system object which works just fine and I can create iviews on without any problems, but when I try to create iViews using a new system object I created (to a different repository) I have no tables available in the "Search Table" drop-down of the iview creation wizard. The system object passed the connection tests (has default alias and working user-mapping), I can't figure out what's the problem.

Please avoid sending me links to the standard documentation; been there, done that, it doesn't deal with this situation, at least not as far as I've seen (if you can prove me wrong that'll be great.)

Any ideas? I know this might be more of a portal question, but I figured at least some of the people here double as portal people too.

Cheers,

Alon

[Former Member]

Hi Alon,

Are the two repositories you are trying to connect to thorugh Portal are on the same MDM server?

And is the repository a Custom defined one or SAP std one?

As in the past few users have faced some problems with creating system objects and iviews with std shipped repositories.

With custom designed rep Ep should work fine if you are using teh latest version of MDM.

- Try restarting the MDM server for the desired rep.

- Try restarting the WAS.

- Make sure the rep you are trying to connect is mounted and loaded.

If its a problem you are facing with the std rep content try creating a custom rep and check to see if its allowing you to create a Sytem object for it or is it throwing the same error.

Check the user mapping and Authorization for that user correctly in portal and MDM too.

Hope It Helped

Thanks & Regards

Simona Pinto

[Former Member]

Hi Alon,

It could be a problem of version mismatch between your deployed files and the EP version.

Refer

Hope it helps.

Thanks,

Minaz

[Former Member]

The issue can't be API version mismatch, nor can it be the user mapping issue -- in both cases the Connection Test in the System object would have failed.

Alon

[Former Member]

Hi Alon,

Thats not true..

Sharing with u a similar issue that we had faced..

Inspite of the connections being established successfully we were not getting the list of repositoris.

The problem was the version incompatibility between the files deployed and the MDM server.

Check with the versions and verify for the compability.

Hope it helps.

Thanks,

Minaz

Edited by: Minaz Kathawala on Jan 8, 2009 1:54 PM

[Former Member]

I am getting the list of repositories, but not the list of tables after I select a repository.

Anyway, the versions are the same, it was the first thing I checked.

Thanks,

Alon

[Former Member]

Hi Alon,

What about the user mapping? User used for the user mapping step cannot have the blank in the password i.e. if you are using Admin user then Admin should have some password defined in the repository.

Try with other repository, if same problem persists then restart the J2EE engine once.

Regards,

Jitesh Talreja

[Former Member]

I know there is a bug, related to the System object and MDM, which caused us to have this problem as well. One of the properties of the System object needs to be changed, consequently the object saved, and the original value put back again and saved again and it should work. Sorry, I cannot trace which field proporty it is right now, but your collegues at SAP should have it documented as well, as it is reported.

[Former Member]

That does sound like an MDM bug

Thanks, I'll follow up with some SAP insiders on this.

[Former Member]

Hi Alon,

Check whether the user mapping has username and password as well because you cannot keep password as blank.

Also check whether the repository is loaded.

Since you can work with other repository then there is no question of version mismatch between MDM Server and the Portal content.

At last just try restarting your Portal server once.

Regards,

Jitesh Talreja