How to config ErrorDistnation with WSLT while offline

Question

I am trying to create a brand new domain for deployment by running a WSLT script in the offline mode.
Below is a snippet of the script
# Individual DLQ cd("/JMSSystemResources/EmailServiceModule/JmsResource/NO_NAME_0")
emailDLQ = create('EmailJMSServer@EmailDLQ','Queue') emailDLQ.setJNDIName('/eh/matchmaker/jms/EmailJMSServer@EmailDLQ') emailDLQ.setSubDeploymentName('EmailQueueSubDeployment')
# Individual queue cd("/JMSSystemResources/EmailServiceModule/JmsResource/NO_NAME_0")
emailQ = create('EmailJMSServer@EmailQueue','Queue') emailQ.setJNDIName('/eh/matchmaker/jms/EmailJMSServer@EmailQueue') emailQ.setSubDeploymentName('EmailQueueSubDeployment') # Set Failure Delivery for queue cd('Queues/EmailJMSServer@EmailQueue') failureParams = create('DeliveryFailureParams','DeliveryFailureParams') failureParams.setRedeliveryLimit(3)
paramsOverrides = create('DeliveryParamsOverrides','DeliveryParamsOverrides')
paramsOverrides.setRedeliveryDelay(900000)
cd('DeliveryFailureParams/NO_NAME_0')
set('ErrorDestination',emailDLQ)
print ls()
Unfortunately, the script generates the following in the JMS config file that fails during AdminServer start up.
<delivery-failure-params>
<error-destination>Proxy for EmailJMSServer1@EmailDLQ: Name=EmailJMSServer1@EmailDLQ, Type=JMSSystemResource!JmsResource!Queue</error-destination>
<redelivery-limit>3</redelivery-limit>
</delivery-failure-params>
The desired value is <error-destination>EmailJMSServer1@EmailDLQ</error-destination>
But set('ErrorDestination','EmailJMSServer1@EmailDLQ') does not work either.
Please help.

Answer 1

Hello Lewis,
It is always a good idea to run the Validator tool to verify a deployment.
The PKCS11.cfg file referenced below is an optional configuration file, that needs to be present/configured if-and-only-if HSM access needs to be enabled on the server.
The error you are seeing below is not something to be concerned about unless you plan to enable HSM access on the server. The stack trace is a DEBUG level log message. If you notice, the INFO log message suggests that this is not a critical error. When such an error is encountered with the PKCS11 config file, the server automatically defaults to not using HSM.
Hope that answers your question.
Regards,
Safdar