Skip to Content

Unable to define a Java system in solman_workcenter

Dear experts,

I am trying to define a Java system in our Solution Manager in order to be able to generate an .xml stack configuration file

for an upgrade. The diagnostics agent has been installed.

I am clicking on Configure System in solman_workcenter, a new web browser opens with a multi-step setup.

I am getting to step 6 to create users. My user store is an ABAP system. At this step, there are 2 users, that need to be

created automatically: SAPSUPPORT and SM_COLL_<SID>.

In the Action combobox, there are only 2 options - Do nothing and Provide Existing User, though no option to create those

users automatically...

The SAPSUPPORT user already exists, as it was created during defining the ABAP system. I have created the SM_COLL_<SID>

user manually in the useradmin panel of Java and I have assigned the suggested roles to it.

I have selected Provide Existing User, typed in the password and after clicking on Execute, the following error pops up:

User J2EE_ADMIN is not allowed to perform this request. Check SAP Note 1647157.

I have googled a little and found SAP Note 1647267 - Solution Manager adaptation to Java UME security, and downloaded

it on our Solution Manager, though it says "Cannot be implemented".

Though there is no way to say that this step is done and the point remains gray. Nevertheless, I decided to continue to the

next step 7, called Configure Automatically. When I click on Execute all, almost all the points are getting green, except for

WEB Services Logical Port Creation. It shows the following error: Java communication user is not operational. Activity aborted.

WHY ?? The user exists and is very well operational... !! Can I skip this point and go ahead ?


PLEASE help me !! Thanks :-)

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Mar 04, 2014 at 07:24 AM

    Hello Symon,

    Error clearly says that , you can not perform this step with administrative user 'J2ee_admin" .

    You can use other id like e.g: your own id .

    Note 1647157 clearly says :

    Due to security reasons, the implicit permissions of the administration user that is created during the installation of an AS Java were removed. No end users, especially no powerful end users, should be able to read or change user data through the SPML service.

    You can also create a user as mentioned in note 1647157 and use to perform this step.

    Hope this helps.

    Regards,
    Archana

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Suhel Khan

      Experienced similiar issue. The user in step 4 was set to a default user instead of techinical. In the UME configuration for DEFAULT user password was set to 90 days. This was the only difference between the two profiles. After chaning the user to Technical I was then able to complete step 6 without any errors.