Perceptive Connector for Microsoft Dynamics AX

Perceptive Connector for Microsoft Dynamics AX Installation and Setup Guide Version: 3.0.x Written by: Product Knowledge, R&D Date: February 2018

Copyright 2017 Hyland Software, Inc. and its affiliates.

Table of Contents About Perceptive Connector for Microsoft Dynamics AX... 4 Required components... 4 Software prerequisites... 4 Conditions for installing the web service... 5 Installation and setup... 5 Download the required files from the Customer Portal... 5 Import Perceptive Connector for Microsoft Dynamics AX model... 6 Install Manage Endpoints utility... 7 Create and configure Windows service endpoints... 7 Configure maximum waiting time for proxy code... 8 Obtain the WSDL URI... 8 Delete an existing AIF service endpoint... 8 Install DAX Connector module for Perceptive Connect Runtime... 9 Configure Dynamics AX settings in Perceptive Connect Runtime Web Console... 9 Configure custom data massaging framework... 10 Create Envoy Services in Perceptive Content 7.1.5... 10 Configure SOAPBridge for Perceptive Content 7.2.2... 11 Configure Envoy support for Perceptive Content 7.2.2... 12 Create a workflow in Perceptive Content... 12 Perform channel mapping in PCR to create PO invoices... 14 Perform channel mapping in PCR to create Non-PO invoices... 14 Perform channel mapping to update the notes... 15 Enable SSL/TLS communication... 16 Uninstall Connector for Dynamics AX from the system... 16 Upgrade Connector for Dynamics AX... 16 Configure support for upgrading to Perceptive Content 7.2.2... 17 Troubleshooting... 17 Index... 19 3

About Perceptive Connector for Microsoft Dynamics AX Perceptive Connector for Microsoft Dynamics AX is a WCF service interfaced with Perceptive Connect Runtime that you can integrate with your application to fetch data from Microsoft Dynamics AX and create an invoice. For example, if you integrate Perceptive Connector for Microsoft Dynamics AX with an eform, it acts as a medium layer that fetches data from Microsoft Dynamics AX to populate fields in the eform. Based on the populated fields, you may create an invoice in Microsoft Dynamics AX. Required components Software prerequisites Before you install Perceptive Connector for Microsoft Dynamics AX, you must have the following software installed on the target computer. The operating system must be Windows Server 2008R2 or Windows Server 2012R2. Microsoft Dynamics AX Server, versions 2012 R3, R3 CU8, R3 CU9, R3 CU10, R3 CU11, R3 CU12 and R3 CU13 Microsoft Dynamics AX AIF services is successfully deployed Microsoft Dynamics AX Client, versions 2012 R3, R3 CU8, R3 CU9, R3 CU10, R3 CU11, R3 CU12 and R3 CU13 Installation of Developer Tools of Microsoft Windows SDK for Windows 7 and.net Framework 3.5 Service Pack 1 which contains SvcUtil.exe component.net Framework 4.5 for AX 2012 R3, R3 CU8, R3 CU9, R3 CU10, R3 CU11, R3 CU12 and R3 CU13 Perceptive Content Server, version 7.1.5.1602 or 7.2.2 Perceptive Content Client, version 7.1.5.1602 or 7.2.2 Perceptive Integration Server, version 7.1.5.1602 or 7.2.2 Perceptive Connect Runtime (PCR), version 1.5.10 Perceptive Content Connector 1.2.30 and Perceptive Content Connector iscript Extension 1.2.30 Note For details, see the Perceptive Content Connector 1.2.x install guide. If you want to use the AP Invoice eform, install AP Invoice eform 12.9.1.x or later for DAX in Perceptive Content 7.1.5.1602 or 7.2.2. For details, see the AP Invoice eform documentation. If you want to use the AP Invoice eform in Perceptive Content 7.2.2, install Perceptive SOAPBridge Connector 1.0.5 or higher in Perceptive Connect Runtime. For details, see the Perceptive SOAPBridge Connector documentation. If you want to integrate Interact for Dynamics AX with the Connector, install Interact for Dynamics AX, version 2.3.2.x. 4

Conditions for installing the web service Before installing the web service, you must complete the following steps to prepare the system. Uninstall any previous version of Perceptive Connector for Microsoft Dynamics AX. Note If you want to save the previous configuration file, create a backup for the DAXConnectorConfiguration.xml file. Ensure that the system where the Manage Endpoints application is installed is located in the same domain as the Microsoft Dynamics AX server. Ensure that during endpoint creation in the Manage Endpoints application, you enter local administrator user credentials in the system where the Manage Endpoints application is installed. Note If you are not a Dynamics AX user, the service cannot communicate with Dynamics AX. To ensure proper communication with Dynamics AX, the local administrator user must be a Dynamics AX user with System Administrator privileges. Ensure that a relevant value for Default company field is set in Dynamics AX server for that user. Ensure that the Windows Tempfolder exists in the system where the Manage Endpoints application is installed. Note To determine the Tempfolder location, type%temp%in Windows Start menu and press Enter. Installation and setup To install and set up Perceptive Connector for Microsoft Dynamics AX, perform the following procedures. 1. Download the required files from the Customer Portal 2. Import Perceptive Connector for Microsoft Dynamics AX model 3. Install DAX Connector module for Perceptive Connect Runtime 4. Install Manage Endpoints utility 5. Create and configure service endpoints automatically Note Uninstall any previous version of Connector for Dynamics AX before installing the latest version. For details, see the section Upgrade Connector for Dynamics AX. Download the required files from the Customer Portal To download the required the files from the Customer Portal, complete the following steps. 1. Navigate to the Customer Portal. 2. On the Product Downloads page, search for the downloadable items for Perceptive Connector for Microsoft Dynamics AX, version 3.0.x. For details, see the Software prerequisites section. 3. Download the PerceptiveConnectorForDynamicsAX_3.0.2.x.zip file to a temporary directory on your computer. 4. After downloading the zip file, right-click it and click Properties>Unblock. Note If the Unblock button is available under Properties, perform the above mentioned step, else ignore the above step. 5. Click Apply>OK. 5

Note If the Unblock button is unavailable under Properties, ignore the above step. 6. Unzip the PerceptiveConnectorForDynamicsAX_3.0.2.zip file to a directory. 7. Open the directory. Ensure that the directory contains the following sub directories. Dynamics AX models PCR components Windows Service components 8. Copy the Windows Service components directory to a specific location on your target machine where the system installs the Windows Service. Note The computer where Windows Service is installed must have Microsoft Windows SDK installed as mentioned above in Software prerequisites section. 9. Based on the Dynamics AX version that you are using, copy the appropriate AX Model file available in the Dynamics AX models directory to a specific location on the target machine where Dynamics AX is installed. 10. Copy the PCR components directory to a specific location on your target machine where the PCR is installed. 11. Copy the DAXConfig sub directory available under PCR components directory to the directory where PCR is installed. Import Perceptive Connector for Microsoft Dynamics AX model Prerequisite If any previous version of Connector for Dynamics AX exists, uninstall the previous version before installing the latest version. For details, see the Upgrade Connector for Dynamics AX section. Before importing the model, close the client connections to the Application Object Server (AOS) instance on which you are working and stop the current AOS instance. If more than one server use the same database, stop all other AOS instances. To import the model, complete the following steps. 1. Navigate to the directory for the management utilities. Typically, the location of this directory is %ProgramFiles%\Microsoft Dynamics AX\60\ManagementUtilities. 2. At the command prompt, type the import command and then press Enter. The import command syntax is axutil import /file:<file name> where <File name> is the absolute path of the Perceptive AX Connector model file. Note The AX model path is the one where you have copied the appropriate AX Model file available in the Dynamics AX models directory. 3. After completion, start the AOS. 4. Open Microsoft Dynamics AX Client. A dialog box appears with the message that the new model has been modified and provides options to run the model as required. 5. To upgrade the model, in the Microsoft Dynamics AX dialog box, perform one of the following actions. If you upload the model for the first time, select Start the model upgrade checklist, click OK, and then proceed with the instructions that follow. If you uploaded the same model before, select Compile and synchronize and click OK. 6

6. Optional. If you selected the Compile and synchronize option, generate the Incremental CIL build from X++ after the compilation and database synchronization are complete. To generate the Incremental CIL build from X++, complete the following substeps. 1. In Microsoft Dynamics AX Client, open New Development Workspace and right-click AOT. 2. Click Add-Ins and then click Incremental CIL generation from X++. When the process is complete, proceed with the usual operations. 7. After importing the model, to deploy the INAPEFormServiceGroup service group, complete the following substeps. 1. In Microsoft Dynamics AX Client, open New Development workspace. 2. Under AOT, under Service Groups, right-click INAPEFormServiceGroup and click Deploy Service Group. Install Manage Endpoints utility To install the Manage Endpoints utility, complete the following steps. 1. Open the Windows Service components directory. 2. Execute the InstallerBatch.bat file as administrator. The Manage Endpoints application appears automatically. Note If required, the user can start the Manage Endpoints application from its desktop shortcut. Create and configure Windows service endpoints You can configure the AX Connector to call one or more Dynamics AX AIF Service Groups. You need to create Windows service endpoints, which act as a bridge between PCR and Dynamics AX. This process is automated through an application that can create and delete Windows service endpoints. To create and configure endpoints, complete the following steps. 1. To start the Manage Endpoints application, on the desktop, right-click the Manage Endpoints application and open it in administrator mode. Note Before performing the above step ensure that you have completed the Manage Endpoints utility installation process. 2. In the Manage Endpoints window, complete the following substeps: 1. Click New. 2. In the Endpoint name box, type the endpoint name used to publish this service. 3. In the Dynamics AX section, in the Endpoint service URL box, enter the Endpoint service URI. Use the WSDL URL of the service that is used to create the invoice, journal, or any other record. The standard format for WSDL URI is listed below. For details, see the Obtain the WSDL URI section. http://<dax server hostname or IP address>:<port number of AIF services>/dynamicsax/services/<service Name>?wsdl 4. In the Windows Service section, in the Service port number box, type the port number used to publish the service. 3. Click Apply to create and save the Windows service endpoint. 7

Note For a single Dynamics AX instance, there is a Windows service and a PCR bundle. For each subsequent Dynamics AX instance, there is a new windows service and a PCR bundle. 4. Enter the Dynamics AX user credentials with System Administrator privileges at the credential prompt. Note In the system, where the Manage Endpoints application is installed, this Dynamics AX user must be a local administrator. If Dynamics AX user information is not available, you can proceed with endpoint creation with the local administrator user credentials. If the AX user information is available, you can set the Dynamics AX System Administrator credentials on the Log On tab in the Properties of the Perceptive Connector AX Service for <fully qualified domain name of AX server> created and then restart the windows service. 5. Copy the Windows service URL available in the Windows service URL box for future use. After installing the DAX Connector module for PCR, paste the copied URL into the Service URL box available in the Microsoft Dynamics AX Configuration Settings under Perceptive Connector for Microsoft Dynamics AX on the Configuration page of Perceptive Connect Runtime web console. 6. Click Close to close the Manage Endpoints utility. Configure maximum waiting time for proxy code During generation of proxy class and config file by Manage Endpoints application, the system may slow down or the process may fail to complete the operation within the scheduled time, which is by default, 1 minute. In such scenarios, you can configure the maximum waiting time for the proxy code. To configure the maximum waiting time for the proxy code, complete the following steps. 1. Go to C:\Program Files (x86)\hyland Software Inc\Perceptive Connector for AX\InstallationDirectory\PerceptiveDAXConnectorWebsite\PerceptiveAIFEndpointsAppGenera tor. 2. Open the Manage Endpoints.exe.config file. 3. In the key named "MaximumTimeToWaitForProxyDllInMilliSec" set the maximum waiting time in milliseconds. 4. Restart the Manage Endpoints application. Obtain the WSDL URI To get the WSDL URI for the Endpoint AIF Service, in Microsoft Dynamics AX, complete the following steps. 1. In the Navigation pane, click System administration. 2. On the System administration area page, under Setup, under Services and Application Integration Framework, click Inbound ports. 3. In the left pane, in the Port name column, select the relevant AIF service and copy the respective WSDL URI. Delete an existing AIF service endpoint To delete an existing AIF service endpoint, complete the following step. In the Manage Endpoints window, select the endpoint and click Delete. 8

Install DAX Connector module for Perceptive Connect Runtime To install DAX Connector module for Perceptive Connect Runtime (PCR), complete the following steps. 1. Go to Perceptive Connect Runtime Dashboard at http://<connectruntime host name>:<port>. 2. In the browser dialog box, type the Connect Runtime user name and password. Note The default login credential is admin. If required, the administrator can change the default login credentials during the Connect Runtime installation process. 3. Go to the PCR components directory which is already copied to the machine where PCR is installed and navigate to the jar sub directory. 4. Install the PerceptiveConnectorforDAX- 3.0.2.jar bundle, which is available in the jar sub directory. Note For details regarding installing connectors, see the Install connectors section of the Perceptive Connect Runtime Installation guide. Configure Dynamics AX settings in Perceptive Connect Runtime Web Console To configure Dynamics AX settings in the Perceptive Connect Runtime Web Console, complete the following steps. 1. On the configuration page, under Perceptive Connector for Microsoft Dynamics AX, click Microsoft Dynamics AX Configuration Settings. 2. Under Microsoft Dynamics AX Connector Configuration section, complete the following substeps. 1. In the DAX Connector service URL box, paste the Windows service URL that you have copied from the Windows service URL box available under Manage Endpoints window. For details, see the Create and configure service endpoints automatically section. 2. In the DAXconfiguration file path box, enter the relevant file path where DAXConnectorConfiguration.xml is available. The file is available in the following location. <PCR install directory>\daxconfig 3. In the PO invoice document service name box, enter the document service name from Dynamics AX server for PO invoices. 4. In the PO invoice document service class name box, enter the document service class name from Dynamics AX server for PO invoices. 5. In the PO invoice document service method name box, enter the document service method name from Dynamics AX server for PO invoices. 6. In the Non-PO invoice document service name box, enter the document service name from Dynamics AX server for non-po invoices. 7. In the Non-PO invoice document service class name box, enter the document service class name from Dynamics AX server for non-po invoices. 8. In the Non-PO invoice document service method name box, enter the document service method name from Dynamics AX server for non-po invoices. 9. In the Apply custom data formatter script? list, select Yes to format the data from AP Invoice eform before sending it to Dynamics AX, else select No. For details, see the Configure custom data massaging framework. 9

10. In the Integrate IDAX? list, select Yes if Interact for Dynamics AX is integrated with the Connector, else select No. 11. In the POinteract form name box, enter the form name from Dynamics AX server. This is applicable only when you select Yes in the Integrate IDAX? list. 12. In the POmethod to execute box, enter the method name to be executed from Dynamics AX server. This is applicable only when you select Yes in the Integrate IDAX? list. 13. In the Non-POinteract form name box, enter the form name from Dynamics AX server. This is applicable only when you select Yes in the Integrate IDAX? list. 14. In the Non-POmethod to execute box, enter the method name to be executed from Dynamics AX server. This is applicable only when you select Yes in the Integrate IDAX? list. 3. Click Save. Configure custom data massaging framework You can configure custom data massaging for Dynamics AX Connector based on Perceptive Connect Runtime. In the data massaging framework, based on your requirement, you can format the data from the AP Invoice eform before sending it to Dynamics AX. The AP_Custom_DAX_Invoice_Operation.js iscript is used for formatting the data from AP Invoice eform. To enable custom data massaging, complete the following steps. 1. Navigate to PCR components directory which is already copied to the machine where PCR is installed. 2. Navigate to the script sub directory. 3. Modify the AP_Custom_DAX_Invoice_Operation.js iscript file to provide your own logic based on the requirement. 4. Copy both AP_Custom_DAX_Invoice_Operation.js and Util_Debug.js iscript files and paste them to the <ImageNow Install Dir>/script folder. Note Ensure that both the iscript file names are not changed. 5. To enable the data massaging framework, in the Apply custom data formatter script? list available in the Perceptive Connect Runtime Web Console, select Yes to format the data from AP Invoice eform before sending it to Dynamics AX. Create Envoy Services in Perceptive Content 7.1.5 You must create Envoy Services in Perceptive Content to enable the communication between Perceptive Content and Dynamics AX Connector. To create the Envoy Services in Perceptive Content, version 7.1.5, complete the following steps. For Perceptive Content 7.2.2 skip the following steps. 1. In the Perceptive Connect Runtime dashboard, click ListSOAP Services. 2. Under Available SOAP services>workflowtrigger, open the available WSDL link on a new tab. 3. Copy the WorkflowTrigger WSDL URL from the address bar for future use. 4. Under Available SOAP services>dynamicsaxconnectorendpoint, open the available WSDL link on a new tab. 5. Copy the DynamicsAXConnectorEndPoint WSDL URL from the address bar for future use. 6. Open the Perceptive Content Management Console. 10

7. If there is no Envoy Service for Workflow Trigger, to enable invoice creation in Dynamics AX, create an Envoy Service for Workflow Trigger with the default name of ASQEndpointService, using the copied WorkflowTrigger WSDL URL. Ensure that all the WorkflowTriggerService operations are selected. Note While copying the WSDL URI ensure that you change the local host to a proper hostname or IP address. The WSDL URI must be in the format http://<hostname>:<port>/ws/workflowtrigger?wsdl. Ensure that the port number is not modified. 8. Create an Envoy Service for eform lookups and validation against Dynamics AX with the default name of DaxPcrWinSvcEnvoyService using the copied DynamicsAXConnectorEndPoint WSDL URL. Ensure that all the DynamicsAXConnectorEndPointService operations are selected. Note If you type a different name for the envoy service, ensure that you specify this name as well as the WSDL URL as the values corresponding to the name and wsdlurl attributes available in the <envoy> tag under <configuration> tag in the AP_Config.xml file. The AP_Config.xml file is available in the <inserver directory>/etc/ap folder location. While copying the WSDL URI ensure that you change the localhost to proper hostname or IP address. The WSDL URI must be in the format http://<hostname>:<port>/ws/dynamicsaxconnectorendpoint?wsdl. Ensure that port number is not modified. Configure SOAPBridge for Perceptive Content 7.2.2 For Perceptive Content 7.2.2, you need to configure the SOAPBridge. To configure the SOAPBridge, complete the following steps. 1. Install PerceptiveSOAPBridge Connector 1.0.5 or higher in Perceptive Connect Runtime. For details, see the Perceptive SOAPBridge Connector documentation. 2. After SOAPBridge is installed, navigate to Perceptive Connect Runtime dashboard and click List REST Services available under RUNTIME INFORMATION. 3. In the available list of REST Services, locate the SOAPBridge entry and copy the WADL link. 4. Inside the Envoy section available under the inow.ini file, corresponding to the pcr.soap.bridge.url, paste the WADL link that you have copied. Note In the system, the inow.ini file is located in <inserver directory>\etc folder where the Perceptive Content is installed. 5. Save the inow.ini file. 6. Go to the <PCR install directory>/conf and open the config.properties file. Add sun* at the end of the value of the org.osgi.framework.bootdelegation.property. The value must be javax.xml.*, org.w3c.dom, org.xml. sax, org.xml. sax.*, com.sun.*, sun.*. 7. Restart the ImageNow service. 8. Restart the PCR service. 11

Configure Envoy support for Perceptive Content 7.2.2 Perceptive Connector for Dynamics AX 3.0.2 supports Perceptive Content version 7.1.5 as well as Perceptive Content version 7.2.2. If you have already upgrade from Perceptive Content version 7.1.5 to perceptive Content version 7.2.2, complete the following steps. 1. Upgrade AP Invoice eform from the version 12.9.0.x to 12.9.1.x or later. For details, see the AP Invoice eform 12.9.x Upgrade Guide. 2. If any earlier version of Perceptive Connector for Dynamic AX is already installed, uninstall it and install Perceptive Connector for Dynamics AX version 3.0.2. 3. Install the SOAPBridge version 1.0.5 or higher. For details see the Configure SOAPBridge for Perceptive Content 7.2.2 section. 4. In the AP_Config.xml file available in the <inserver directory>/etc/ap folder location, locate the <envoy>tag under the <configuration> tag and complete the following substeps. 1. Inside the <envoy> tag, corresponding to the name attribute, enter the name of the Envoy service that you want to create. 2. Inside the <envoy> tag, corresponding to the wsdlurl attribute, enter the DynamicsAXConnectorEndPoint WSDL URL of the PCR DAXConnector service to which you want to connect. Note In the Perceptive Connect Runtime dashboard, click List SOAP Services. Under Available SOAP services>dynamicsaxconnectorendpoint, open the available WSDL link on a new tab. Copy the DynamicsAXConnectorEndPoint WSDL URL from the address bar. 5. Open services.msc and restart ImageNow Server 7.2 (Primary) service. 6. Open the command prompt as administrator, navigate to the <inserver install directory>/bin64 folder and run the intool --cmd run-iscript --file AP_Maintenance.js command. Note The above mentioned command creates an envoy with the details mentioned above in step 4. If you want to modify the wsdlurl of an existing envoy, delete the same envoyusing iscript, enter the new wsdlurl inside the <envoy> tag in the AP_Config.xml file, and then run the intool --cmd run-iscript --file AP_Maintenance.js command. Create a workflow in Perceptive Content Prerequisite Ensure that you have installed and correctly configured the Perceptive Content server, Integration Server, Perceptive Connect Runtime (PCR) and Perceptive Content Connector along with Perceptive Content Connector iscript Extension. To create a workflow, complete the following steps. 1. Add a workflow process with a suitable name. 2. Create a DAX Processing queue by dragging a Work queue to the process diagram inside the created workflow and name the queue as DAX Processing. 3. Create a DAX Success queue by dragging a Work queue to the process diagram inside the created workflow and name the queue as DAX Success. 4. Create a DAX Failure queue by dragging a Work queue to the process diagram inside the created workflow and name the queue as DAX Processing Failure. 5. Create a Content Failure queue by dragging a Work queue to the process diagram inside the created workflow and name the queue as DAX Submit Failure. 12

Note If you provide different names for the above queues, ensure that you specify those names in the sample channel input and output mapping files. 6. If you are using Perceptive Content 7.1.5.1602, complete the following substeps. 1. Create an Integration Queue for PO inside this workflow and double-click the queue. 2. In the Queue Properties dialog box, in the Name box, type the queue name for PO. 3. In the Automated Action section, complete the following actions. Under Success Action, in the Queue list, select the DAX Processing queue. Under Failure Action, in the Queue list, select the DAX Submit Failure queue. Under Envoy Service, in the Service Operation Name list, select ASQEndpointService. 4. Click OK. 5. Similarly, to create an Integration queue for Non-PO, under Queues, drag an Integration queue for Non-PO to the process diagram and double-click the queue. 6. In the Queue Properties dialog box, in the Name box, type the queue name for Non-PO. 7. In the Automated Action section, complete the following actions. Under Success Action, in the Queue list, select the DAX Processing queue. Under Failure Action, in the Queue list, select the DAX Submit Failure queue. Under Envoy Service, in the Service Operation Name list, select ASQEndpointService. 8. Click OK. 7. If you are using Perceptive Content 7.2.2, complete the following substeps. 1. Create a Connect Queue for PO inside this workflow and double-click the queue. 2. In the Queue Properties dialog box, in the Name box, type the queue name for PO. 3. In the Automated Action section, complete the following actions. Under Success Action, in the Queue list, select the DAX Processing queue. Under Failure Action, in the Queue list, select the DAX Submit Failure queue. 4. Click OK. 5. Similarly, to create a Connect ASQ for Non-PO, under Queues, drag the Connect queue for Non- PO to the process diagram and double click the queue. 6. In the Queue Properties dialog box, in the Name box, type the queue name for Non-PO. 7. In the Automated Action section, complete the following actions. Under Success Action, in the Queue list, select the DAX Processing queue. Under Failure Action, in the Queue list, select the DAX Submit Failure queue. 8. Click OK. 9. Inside inserverworkflow.ini file, under the General section, locate connect.uri and enter the URL of the Workflow Trigger REST wadl. 13

Note In the system, the inserverworkflow.ini file is available in C:\inserver\etc folder where Perceptive Content is installed. In the Perceptive Connect Runtime dashboard, in the List REST Services, locate the workflow Trigger entry and find the value for Workflow Trigger REST wadl. 10. Save the file. 11. Restart the ImageNow Server 7.2 service. 12. Restart the ImageNow Workflow Agent 7.2 service. Perform channel mapping in PCR to create PO invoices In Perceptive Connect Runtime, to create a channel for PO invoices, complete the following steps. 1. Click Create a Channel and provide a name. 2. In the Trigger list, select Integration ASQ Trigger. 3. In the Workflow Queue ID box, type the Integration queue ID of the PO ASQ that was created previously. 4. Click Continue. 5. In the Actions list, select CreateInvoiceAction available in the Perceptive Connector for Microsoft Dynamics AX section. 6. Copy the content of CreateInvoiceActionPO_input.xml file and paste it into the Inputs section. 7. Click Save Inputs. 8. Click Enable Channel. Note There is no need to change the output mapping. Connect Runtime performs a validation check on both the input and output data mapping. The CreateInvoiceActionPO_input.xml file is available in the sample mappings sub directory under PCR components directory. Perform channel mapping in PCR to create Non-PO invoices In Perceptive Connect Runtime, to create a channel for Non-PO invoices, complete the following steps. 1. Click Create a Channel and provide a name. 2. In the Trigger list, select Integration ASQ Trigger. 3. In the Workflow Queue ID box, type the Integration queue ID of the Non-PO ASQ that was created previously. 4. Click Continue. 5. In the Actions list, select CreateInvoiceAction available in the Perceptive Connector for Microsoft Dynamics AX section. 6. Copy the content of CreateInvoiceActionNonPO_input.xml file and paste it in the Inputs section. 7. Click Save Inputs. 8. Click Enable Channel. Note There is no need to change the output mapping. Connect Runtime performs a validation check on both the input and output data mapping. The CreateInvoiceActionNonPO_input.xml file is available in the sample mappings sub directory under PCR components directory. 14

Perform channel mapping to update the notes In Perceptive Connect Runtime, to create a channel for both PO and Non-PO invoices, complete the following steps. 1. Click Create a Channel and provide a name. 2. In the Trigger list, select Update Document Trigger. 3. In the Process Identifier box, type GLOBAL. 4. Click Continue. 5. In the Actions list, select UpdateDocumentAction available in Perceptive Connector for Microsoft Dynamics AX section. 6. Copy the content ofupdatedocumenttrigger_input.xml file and paste it in the Inputs section. 7. Click Save Inputs. 8. Copy the content ofupdatedocumenttrigger_output.xml file and paste it in the Outputs section. In the Outputs section perform the following optional substeps. 1. Optional. After processing the invoice, if no update is required in the document notes, remove the following code snippet from the Outputs section. <c:parameter> <c:name>documentnotes</c:name> <in:documentnoteswriter> <in:docid>docid</in:docid> <in:mode>set</in:mode> </in:documentnoteswriter> </c:parameter> 2. Optional. If no update is required in the Custom Property, remove the following code snippet from the Outputs section. To update a specific Custom Property, provide the name of the Custom Property in the corresponding Name field. The journal number or table reference ID is automatically populated beside the Custom Property that is updated. <c:parameter> <c:name>documentcustprop</c:name> <in:objectpropertywriter> <in:name>customer Property Name</in:name> <in:objectid>docid</in:objectid> <in:objecttype>document</in:objecttype> <in:propertytype>customproperty</in:propertytype> <in:ignoremissingproperty>true</in:ignoremissingproperty> </in:objectpropertywriter> </c:parameter> 9. Click Save Outputs. 10. Click Enable Channel. Note The names in the UpdateDocumentTrigger_input.xml file must be identical to the queue names provided in the DAX Success and DAXProcessing Failure queues. The acceptable mode values in the UpdateDocumentTrigger_output.xml file are SET, APPEND and PREPEND. For details, see the Perceptive Content Connector Installation Guide. The Process Identifier and all the entries in the mapping files are case sensitive. The UpdateDocumentTrigger_input.xml and the UpdateDocumentTrigger_output.xml files are available in the sample mappings sub directory under PCR components directory. 15

Enable SSL/TLS communication To make PerceptiveConnectorforDAX-3.0.2 compatible with Perceptive Content 7.1.5 or 7.2.2, you have to enable SSL/TLS communication as Perceptive Content 7.1.5 and 7.2.2supportsecured transaction only. For details, see the Configure SSL sections in the Content installation guide, Content Connector installation guide, Connect Runtime installation guide and Integration Server installation guide. Uninstall Connector for Dynamics AX from the system To uninstall Perceptive Connector for Microsoft Dynamics AX from the system, complete the following steps. 1. Delete all the existing endpoints from the Manage Endpoints application. 2. Close the Manage Endpoints application. 3. Close all the folders that are already opened on your system. 4. Delete the Hyland Software Inc directory from C:\Program Files (x86)\. 5. Delete the Manage Endpoints shortcut from your desktop and Start menu. 6. Uninstall the PerceptiveConnectorforMicrosoftDynamicsAX bundle from PCR. For details, see the Perceptive Connect Runtime Installation guide. 7. Delete the Perceptive AX Connector model from Dynamics AX. For details, refer to Upgrade Connector for Dynamics AX. Upgrade Connector for Dynamics AX To upgrade Connector for Dynamics AX from 2.x to 3.x, you must delete any existing AX models named Perceptive AX Connector and then import the new Perceptive AX Connector model, version 3.0.2.x. Prerequisite Before deleting the model, close the client connections to the Application Object Server (AOS) instance on which you are working and stop the current AOS instance. If more than one server use the same database, stop all other AOS instances. To delete any existing AX models, complete the following steps. 1. Open the command prompt as administrator. 2. At the command prompt, navigate to the directory for the management utilities. Typically, the location of this directory is %ProgramFiles%\Microsoft Dynamics AX\60\ManagementUtilities. 3. At the command prompt, type the delete command and then press Enter. The delete command syntax is axutil delete /model:<model ID> where <Model ID> is the ID of the Perceptive AX Connector. You can find the Model ID of Perceptive AX Connector by executing the command axutil list to locate the particular Perceptive AX Connector model and note it s ID. At the command prompt, type y. 4. Start the AOS. 5. Open Microsoft Dynamics AX Client. A dialog box appears with the message that the model was modified and provides options to run the model as required. 6. In the dialog box, select the relevant option and follow the instructions in the wizard. 16

Note It is recommended to execute the full compilation, full CIL generation and Database synchronization whenever the model store is modified. After database synchronization you must restart the AOS. 7. If you are using Perceptive AX Connector 2.4.x.x, delete all the Windows service endpoints from the Manage Endpoints utility application. 8. From the Control Panel, uninstall the program PerceptiveConnectorforMSDynamicsAXSetup_2.x.x.x.exe. 9. Follow the installation steps as discussed in the Installation and setup section. Configure support for upgrading to Perceptive Content 7.2.2 Perceptive Connector for Dynamics AX 3.0.2 supports Perceptive Content version 7.1.5 as well as Perceptive Content version 7.2.2. If you have already upgraded from Perceptive Content version 7.1.5 to Perceptive Content version 7.2.2, complete the following steps. 1. Upgrade AP Invoice eform from version 12.9.0.x to 12.9.1.x or later. For details, see the AP Invoice eform 12.9.x Update Guide. 2. If any earlier version of Perceptive Connector for Dynamic AX is already installed, uninstall it and install Perceptive Connector for Dynamics AX version 3.0.2. 3. Install the SOAPBridge version 1.0.5 or higher. For details, see the Configure SOAPBridge for Perceptive Content 7.2.2 section. Troubleshooting If you face any issue during installation, you can use the relevant log files. To troubleshoot, complete the following actions. If any AP eform related problem occurs, check the AP eform logs and verify whether the values from Dynamics AX are populated correctly in the logs. Typically, the path of the AP eform log file is <inserver install directory>/logs. For any basic entry level issue, check the PCR logs. You can also check the PCR logs from the PCR UI. The path of the PCR log file is <PCR install directory>/logs. If no error log is found in the PCR logs, check the Windows service logs. It can happen that the WCF service hosted on the Windows service fails, to identify the actual error that is returned by the WCF service, you must check the Windows service logs. Typically, the path of the Windows service log file is C:/Program Files (x86)/hyland Software Inc/Perceptive Connector for AX/logs. The following two types of log files are available in this location. PCRConnectorForAX_WindowsService_<yearmonthday>.log - This contains any error that is detected during the WCF service calls to Dynamics AX. PerceptiveConnectorLibraryGenerator_<yearmonthday>.log - This contains any error that occurs while creating an endpoint using the Manage Endpoints application. If the Connector fails to create an invoice in Dynamics AX or fetch a query result from Dynamics AX, and no proper error logs appear in Windows Service or PCR, then the issue is from the Dynamics AX end. To troubleshoot, perform the following steps. 1. After opening the AX client, navigate to System administration>periodic>services and Application IntegrationFramework>Exceptions. 17

2. Find your issue under Exceptions. 3. Click the General tab to see the detailed exception message. 18

Index Channel mapping Non-PO invoices, 14 PO invoices, 14 Update notes, 15 Envoy Service creation Create Envoy Services, 10 Import Connector for MSDAX model, 6 Install Manage Endpoint utility, 7 Install and setup Perceptive Connector for Microsoft Dynamics AX, 5 Install DAX Connector module Perceptive Connect Runtime, 9 Manage Endpoint utility installation, 7 Software prerequisites, 4 Uninstall Connector for Dynamics AX, 16 Version upgrade Connector for Dynamics AX, 16 Web service installation conditions, 5 Windows service endpoints Create and configure, 7 Workflow creation, 12 19