Hi Bobby
You can so something is wrong with your configuration probably that you don't reach this point. Yuksel comment is correct in terms of what you're supposed to have according to SAP.
However, for the sake of training or looking at SolMan 7.2, whatever purpose you're at, if you don't run the AS JAVA stack, you can still configure SolMan but some functionality won't be available such as Agent Connectivity, Root Cause Analysis (mostly) because that functionality resides on the AS JAVA stack.
Besides that, if you've only got AS ABAP stack running, you can configure the SolMan (outside of what I mentioned before) so if you want to check out Solution Documentation, CHARM, whatever else outside of what needs agent connectivity (so technical monitoring won't function properly without AS JAVA running) you can do that.
Not sure what happens when you call it up, you say the SICF service is active so that makes me wonder if your HTTP configuration is properly done or set. Can you call up another transaction that uses HTTP or can you test ping service for example and get a decent response back? Might be related to hostname / SMICM configuration so please check the logs over there and see if you can get it to work properly. You could HTTP trace in your browser to catch a clue to why it doesn't function as well, otherwise check SMICM logging, SM21, ST22 etc to see why this issue exists.
Best regards
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.