Creating the Activation Specifications

You need to create several Activation Specifications for your SIMULIA Execution Engine installation.

  1. Under Resources/JMS on the left side of the console, click Activation specifications.
  2. From the All scopes list, select Cell=<server_name><node_number>Cell.
  3. Click New.
  4. Verify that Default messaging provider is selected.
  5. Click OK.
  6. In the Name text box, type the following entry:

    job

  7. In the JNDI name text box, type the following entry (this setting is case-sensitive):

    fiper/act/job

  8. From the Destination type list, verify that Queue is selected.
  9. In the Destination lookup text box, type the following entry:

    fiper/jms/job

    This entry represents the JMS topic name that matches the current entry. These settings are case-sensitive, just like the original JNDI name settings.

  10. From the Bus name list, select Fiper Bus.
  11. In the Maximum batch size text box, verify that 1 appears.
  12. In the Maximum concurrent MDB invocations per endpoint text box, verify that 10 appears.
  13. From the Authentication alias list, select the appropriate alias. You may need to scroll down to see this option.

    Note: This setting is necessary if security will be enabled on your SIMULIA Execution Engine, but it will not impact a non-secure SIMULIA Execution Engine.

  14. Click OK.
  15. Repeat step 3 through step 14 for each of the following specifications, replacing the information shown below in the corresponding steps (all other settings are the same as described above):

    Create the following activation specifications:

    Name: log

    JNDI name: fiper/act/log

    Destination JNDI name: fiper/jms/log

    Maximum concurrent MDB invocations per endpoint: 10

    Name: stationrequest

    JNDI name: fiper/act/stationrequest

    Destination JNDI name: fiper/jms/stationrequest

    Maximum concurrent MDB invocations per endpoint: 10

    Name: stationrequestlarge

    JNDI name: fiper/act/stationrequestlarge

    Destination JNDI name: fiper/jms/stationrequest

    Maximum concurrent MDB invocations per endpoint: 2

    Name: task

    JNDI name: fiper/act/task

    Destination JNDI name: fiper/jms/task

    Maximum concurrent MDB invocations per endpoint: 1

    Name: task2

    JNDI name: fiper/act/task2

    Destination JNDI name: fiper/jms/task

    Maximum concurrent MDB invocations per endpoint: 1

    Name: task3

    JNDI name: fiper/act/task3

    Destination JNDI name: fiper/jms/task

    Maximum concurrent MDB invocations per endpoint: 1

    Name: workflow

    JNDI name: fiper/act/workflow

    Destination JNDI name: fiper/jms/workflow

    Maximum concurrent MDB invocations per endpoint: 10

    Name: workflowlarge

    JNDI name: fiper/act/workflowlarge

    Destination JNDI name: fiper/jms/workflow

    Maximum concurrent MDB invocations per endpoint: 2

    Name: workitem

    JNDI name: fiper/act/workitem

    Destination JNDI name: fiper/jms/workitem

    Maximum concurrent MDB invocations per endpoint: 10

    Name: workitemlarge

    JNDI name: fiper/act/workitemlarge

    Destination JNDI name: fiper/jms/workitem

    Maximum concurrent MDB invocations per endpoint: 2

    Name: jobmonitor

    JNDI name: fiper/act/jobmonitor

    Destination JNDI name: fiper/jms/jobmonitor

    Maximum concurrent MDB invocations per endpoint: 10

    Your list of Activation Specifications should appear similar to the following:



  16. Save the configuration.