Sure it is 7.5.1? any test fixes? check the help->About ... what build is it?

... also, make sure to use the client library from that server.

Just an FYI:

7.5.1 and 7.5.1.1 are not the same in RAM. Also just the testfix number would be sufficient. We don't need the list of actual defects. So you can say simply RAM 7.5.1.1 testfix 7d.

We need to know this information on any RAM question. This is because there are many different levels of RAM out there and they all have many differences from the previous ones.

I'll go see if I can see any problems with testfix 7 that would cause this.

Thanks.

OK, we have another problem. The version of RAM you gave us was naturally the server version. The problem is that your error is occurring in the ramclient and not the server. Your ramclient does not appear to be from 7511. The line numbers don't quite match up.

So can you please do the following, look in the directory where you are storing your ramclient.zip jars and tell me:

a) The entire name of the jar that starts with the name com.ibm.ram.common?
b) Are there any files in this directory labeled something like testfix12RamClient.xml? What are they named?
c) Open the ramclient.jar and go to the META-INF\MANIFEST.MF file and tell me what the Created-By: entry in the manifest says?

These three together will tell me the version of the ramclient being used.

Thanks

Ah, you are using an internal build that has never been published. I'm not sure why it is failing.

Did you do a session.release() somewhere between the

session.getCategorySchema(CustomPolicyConstants.BUSINESS_CAPABILITY_CATALOG);

and the

getRAMSession().put(categorySchema, new RAMStatusMonitor());

That is the only way I could see an NPE at the given location.

   public static RAMSession getRAMSession() {
        RAMSession session = new RAMSession("https://10.42.102.20:11602/ram.ws","fvz857", "fvz857");
        return session;
    }

Every time you call getRAMSession() you are getting a brand new one. So the
getRAMSession().getCategorySchema() is a different ram session than the one retrieved via getRAMSession().put(...). You can't get a schema from one session and try to put it into a different session.

Not only that but you are leaking RAMSession's. You are required to do a session.release() on every RAMSession created. If you don't then session will leak and not logout.

Thanks,
Rich

I don't know what that means.  What is the "catalog hierarchy" and how are you getting it?

Does the show up on the host if you looked there?

That is a cached view. It is refreshed approximately once every ten minutes.

You need to first verify that the update actually worked on the host. Go to the Admin pages and verify that the schema has been updated. That view always shows the live current view. If that worked, then it will eventually show up on the search page.

My understanding is that the category is missing from the visual browse.  Does it show up on the search page when you drill down to it?

For Visual Browse top category to show up there must be at least one asset that has some child node of the category assigned to it. Until then nothing shows. But once there is at least one then it will show them all. BUT you need to close the visual browser after making the change. The categories for the visualbrowse are only retrieved once, when the browser is started. You need to close and reopen it to see the new sub-category.