# MQ configurations are not extracted for Open Liberty targets

If MQ configurations are not extracted for Open Liberty targets, use the
following workaround:

1. Extract the `wmq.jmsra.rar` file from the source VM by adding it to the migration plan.

       applications:
       - appName: brownear-ear
         httpEndpoints:
         - httpPort: 9080
           httpsPort: 9443
           id: defaulthttpendpoint
         image:
           name: brownear-ear
       includeFiles:
       - /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar

2. Edit the server XML file to ensure following features are included in the feature manager:

         <featureManager>
           <feature>ejb-3.2</feature>
           <feature>jms-2.0</feature>
           <feature>mdb-3.2</feature>
           <feature>localConnector-1.0</feature>
           <feature>jaxrs-2.1</feature>
           <feature>cdi-2.0</feature>
         </featureManager>

3. In the same file, ensure that the username and password are set for `jmsActivationSpec`:

         <jmsActivationSpec ...>
           <properties.mqJmsRa ... userName="USER_NAME" password="PASSWORD"/>
         </jmsActivationSpec>

   > [!NOTE]
   > **Note:** You need to set `includeSensitiveData` to `true`.

   > [!NOTE]
   > **Note:** these username and password also can be found in the `wsadmin.py` artifact.

4. In addition, it's possible a JNDI issue may occur, which you'll need to
   resolve according to the error message.