Navigation

    Best APM Solution for Oracle WebLogic Server & FMW Product Family
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Download

    SOLVED Unable to monitoring WLSDM Agent Version and Agent Compatibility.

    General Support & Troubleshooting
    2
    3
    39
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • wlcommunityusers
      wlcommunityusers last edited by

      Unable to monitor WLSDM Agent Version and Agent Compatibility in Monitor WLSDM Agents tab. WLSDM log throws the following error. How can I solve this problem.

      Screenshot
      980648a5-5d28-4e12-9bc4-0f54d8f0b058-image.png

      WLSDM Log:

      javax.naming.NoPermissionException: User <anonymous> does not have permission on wlsdm_agent_remote_operation to perform lookup operation.
      	at weblogic.utils.StackTraceDisabled.unknownMethod()
      >
      ####<Feb 2, 2023 3:06:46 PM CST><SEVERE><WLSDM><BEA-000000><User <anonymous> does not have permission on wlsdm_agent_remote_operation to perform lookup operation.
      
      javax.naming.NoPermissionException: User <anonymous> does not have permission on wlsdm_agent_remote_operation to perform lookup operation.
      	at weblogic.utils.StackTraceDisabled.unknownMethod()
      >
      ####<Feb 2, 2023 3:06:59 PM CST><WARNING><WLSDM><BEA-000000><Has No Valid License. Caused by null/wrong license info.>
      ####<Feb 2, 2023 3:07:14 PM CST><WARNING><WLSDM><BEA-000000><Has No Valid License. Caused by null/wrong license info.>
      ####<Feb 2, 2023 3:07:16 PM CST><SEVERE><WLSDM><BEA-000000><User <anonymous> does not have permission on wlsdm_agent_remote_operation to perform lookup operation.
      
      javax.naming.NoPermissionException: User <anonymous> does not have permission on wlsdm_agent_remote_operation to perform lookup operation.
      	at weblogic.utils.StackTraceDisabled.unknownMethod()
      
      1 Reply Last reply Reply Quote 0
      • D
        Deniz Bedel - WLSDM Team last edited by

        By default the JNDI resource is controlled by the Group: everyone policy and therefore anyone can access the resource using any method such as search or list. You need to make this authorization for WSDM. You can easily solve this problem by following the steps below:

        1. Click on the managed server in the “RUNNING” state on WebLogic Consol.
        2. Click on the “View JNDI Tree” link just below the Configuration --> General tab.
          b7ac04ff-f87d-4100-9701-a81cda39e599-image.png
        3. Switch to Security --> Policies tab from the “JNDI Tree Structure” page.
        4. Select “ALL” from the “Methods” drop-down list and click the “Add Conditions” button under the “Policy Conditions” heading.
          bd632ff2-d19b-4449-9cdb-cfe46a10aeba-image.png
        5. Select “Group” from the “Predicate List” drop-down list. Click “Next”.
        6. Type everyone in the Group Argument Name: Textbox and click “Add” button.
          c098eb25-f8ca-46c9-b7f9-ad615795a666-image.png
        7. Click Finish.

        After the settings, Group : everyone will appear under Policy Conditions. Repeat these settings for each Managed Server where WLSDM Arguments are entered and restart all managed servers sequentially. Restart the Admin Server last. You will see that the problem is solved.

        3412ed1a-f568-4ad8-8af4-6c25d57ccea1-image.png

        98df401b-018c-4c00-ade5-4e989ce7ae5b-image.png

        Best regards

        1 Reply Last reply Reply Quote 0
        • wlcommunityusers
          wlcommunityusers last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • D
            Deniz Bedel - WLSDM Team last edited by

            By default the JNDI resource is controlled by the Group: everyone policy and therefore anyone can access the resource using any method such as search or list. You need to make this authorization for WSDM. You can easily solve this problem by following the steps below:

            1. Click on the managed server in the “RUNNING” state on WebLogic Consol.
            2. Click on the “View JNDI Tree” link just below the Configuration --> General tab.
              b7ac04ff-f87d-4100-9701-a81cda39e599-image.png
            3. Switch to Security --> Policies tab from the “JNDI Tree Structure” page.
            4. Select “ALL” from the “Methods” drop-down list and click the “Add Conditions” button under the “Policy Conditions” heading.
              bd632ff2-d19b-4449-9cdb-cfe46a10aeba-image.png
            5. Select “Group” from the “Predicate List” drop-down list. Click “Next”.
            6. Type everyone in the Group Argument Name: Textbox and click “Add” button.
              c098eb25-f8ca-46c9-b7f9-ad615795a666-image.png
            7. Click Finish.

            After the settings, Group : everyone will appear under Policy Conditions. Repeat these settings for each Managed Server where WLSDM Arguments are entered and restart all managed servers sequentially. Restart the Admin Server last. You will see that the problem is solved.

            3412ed1a-f568-4ad8-8af4-6c25d57ccea1-image.png

            98df401b-018c-4c00-ade5-4e989ce7ae5b-image.png

            Best regards

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • First post
              Last post

            WLSDM: Native WebLogic Monitoring & Diagnostics

            Copyright © 2021 WLSDM Community & Support Portal | WLSDM.COM | WLSDM Blog