Automic Workload Automation

  • 1.  SMGR_PORT_RANGE parameter not documented correctly

    Posted Feb 13, 2018 08:49 AM

    If you find the following error in the WP log file:

    U00011830 Invalid value: '(8871, 8872)' in 'UC_SYSTEM_SETTINGS' / 'SMGR_PORT_RANGE'. Default value: '0000008871' will be used.

    you have a space in your SMGR_PORT_RANGE parameter in your UC_SYSTEM_SETTINGS variable.

    Simply remove the blank space from your SMGR_PORT_RANGE in your UC_SYSTEM_SETTING so that the correct values are considered.

    Unfortunately, this is also wrongly documented in our online documentation for v12 and v12.1.1 The documentation shows as an example a blank character, which must not exist. The problem has already been reported to our documentation department to resolve it.


  • 2.  SMGR_PORT_RANGE parameter not documented correctly

    Posted Feb 13, 2018 09:34 AM
    I pointed out the problem with the space after the comma four years ago. And more than two years ago, I proposed the following improvements to the documentation of SMGR_PORT_RANGE:
    The description of SMGR_PORT_RANGE could be improved:
    1. Instructions relevant to the Automic Web Interface should be added.
    2. The termport area should be replaced with the phraserange of port numbers.
    3. In the example, the space after the comma should be removed.
    4. The termService Managershould be two words.
    5. An explanation should be provided about what details are updated by the Service Manager scan.
    Here is my proposed revision:

    If a Service Manager is used, you can execute its commands (e.g., starting or stopping a process) directly via the AE system. The relevant commands can either be executed directly from the Process & Usage page of the Administration perspective in the Automic Web Interface, via the Agents → Automation Engine section of the System Overview in the Java User Interface, or via the script element MODIFY_SYSTEM.

    In order for the AE to be able to execute Service Manager commands, the AE must know the details of the respective Service Manager-managed process:

    • The host name where the Service Manager process is running (inferred from the respective server or agent object).
    • The port number on which the Service Manager is listening
    • The phrase used to start the Service Manager
    • The name of the process started by the Service Manager

    These details can be specified manually, by editing the respective server or agent object in the system client (client 0). Or they can be discovered automatically, through a Service Manager scan.

    The SMGR_PORT_RANGE key specifies the port number (or a contiguous range of port numbers) that will be scanned during a Service Manager scan. When a Service Manager scan is initiated, the Automation Engine will connect to the specified port (or range of ports), and will attempt to discover the above details about the selected server or agent process automatically.

    The AE system automatically scans for a Service Manager when the server processes start for the first time. Subsequently, this scan can be executed manually using the Verify connection to Service Managercommand in the Administration perspective (AWI), or using theRefresh Service Manager Scancommand in the System Overview (Java UI).

    To specify a range of port numbers, provide the start port and end port, separated by a comma, and enclosed in parentheses. The range of port numbers is contiguous, and includes both the start and end port. The range of port numbers must not exceed 10 port numbers.  It is not possible to specify multiple non-contiguous port numbers, or multiple ranges or port numbers.

    For example: (8871,8873)
    Default value: 8871

    Karin_Wasinger_8156: perhaps you would be so kind as to pass this along to the folks responsible for correcting & updating the documentation. Note that the text includes details relevant to the Java User Interface.


  • 3.  SMGR_PORT_RANGE parameter not documented correctly

    Posted Feb 13, 2018 09:37 AM

    And don’t forget to vote for this idea if you like it:

    SMGR_PORT_RANGE should accept multiple ranges of port numbers

    SMGR_PORT_RANGE specifies a single port or contiguous inclusive range of port numbers  that the AE server scans for an active service manager process when a  service manager scan is initiated (either automatically or manually).

    It should be possible to specify:
    1. Multiple non-contiguous single port numbers;
    2. Multiple ranges of port numbers; and
    3. More than ten port numbers.

    E.g.,
    22020,22050-22059
    8816,8819,8820-8824,8830-8834


  • 4.  RE: SMGR_PORT_RANGE parameter not documented correctly

    Posted Mar 02, 2023 03:33 PM

    what about these from v21.0.5   ?



    ------------------------------
    Olgun Onur Ozmen
    https://www.linkedin.com/in/olgunonurozmen/
    ------------------------------



  • 5.  RE: SMGR_PORT_RANGE parameter not documented correctly

    Broadcom Employee
    Posted Mar 03, 2023 02:18 AM

    Hi,

    what is the exact value you are having defined in UC_SYSTEM_SETTINGS? What happens if you select "Update Service Manager Link" from the AWI?

    If you are seeing any error message when updating the link kindly open a case with support.

    Thank you!

    Regards, Markus




  • 6.  RE: SMGR_PORT_RANGE parameter not documented correctly

    Posted Mar 03, 2023 04:53 AM

    yes we got error --> U00003335 Process with Process ID 'xxxx' is not available in the Service Manager.

    i opened the  Case#33364487



    ------------------------------
    Olgun Onur Ozmen
    https://www.linkedin.com/in/olgunonurozmen/
    ------------------------------



  • 7.  RE: SMGR_PORT_RANGE parameter not documented correctly

    Posted Mar 03, 2023 03:26 AM

    Hi Olgun,

    it looks like that you are not using parentheses. Please try this value:

    (8871,8872)

    regards,
    Peter



    ------------------------------
    Automic Certified Professional/Expert & Broadcom Knight

    For AUTOMIC trainings please check https://www.qskills.de/qs/workshops/automic/
    ------------------------------



  • 8.  SMGR_PORT_RANGE parameter not documented correctly

    Posted Feb 13, 2018 09:45 AM
    supported...


  • 9.  RE: SMGR_PORT_RANGE parameter not documented correctly

    Posted Mar 03, 2023 05:49 AM

    Thanks, but Broadcom deleted the idea last year, along with many others.

    Broadcom has announced that it will replace the Service Manager in the future, and will not invest time in improving it.