ILINX Export supports the Microsoft Cluster Service (MSCS) for High Availability. MSCS provides the ability for a group of independent servers to be managed as single system. ILINX Export is a Cluster-Unaware Service and relies on the Generic Service Resource Type to manage services as a cluster.
From time to time I receive questions about large file uploads with ILINX Capture. ILINX Capture can upload files of any size. The limitation is within Internet Information Services(IIS) and or the amount of memory installed in the web server. This is not only true for ILINX Capture, but and ASP or ASP.Net application.
This example demonstrates how to use a .Net Web Service WebLookup in the ILINX Capture Client. The sample C# project can be downloaded at http://downloads.ilinxcapture.com/samples/ilinxweblookupsample.zip. You will need to create an ILINX Document Type with at least the following three fields.
- Client Account Number
- Document Type
- Sub Type
This example only returns the following XML String to ILINX Capture to populate the 3 index values. The XML string is in the same format that was provided to us from the ProcessXML Function parameter IndexXML. The Value node of the XML is the index data that is then populated in the web client. This data can be manipulated in many ways before returning to the calling ILINX Capture Web Client.
<ILINX><IndexList><Index><Name>Client Account Number</Name><Label>Client Account Number</Label><ReadOnly>0</ReadOnly><Visible>1</Visible><Value>Client Account Number</Value></Index><Index><Name>Document Type</Name><Label>Document Type</Label><ReadOnly>0</ReadOnly><Visible>1</Visible><Value>Document Type</Value></Index><Index><Name>Sub Type</Name><Label>Sub Type</Label><ReadOnly>0</ReadOnly><Visible>1</Visible><Value>Sub Type</Value></Index></IndexList></ILINX>
To use the web service it must be published to an IIS Web Server. Once published to the web server you must access the web service and generate a WSDL file.
1. Navigate to the new Web Service ASMX file, for example: http://lptbryan/ilinxweblookupsample/ilinxweblookupsample.asmx?wsdl
2. Save this file to the C:\inetpub\ILINX\QXServices or equivalent in your environment as the filename.WSDL, for example ilinxweblookupsample.WSDL
3. Open the newly created file with a text editor like notepad and modify the ProcessXMLResponse section. Chagne ProcessXMLResult to Result.
Original WSDL File
Does your ECM server seem to have performance related issues? Are requests to your ECM software taking longer than normal? If so then you may have a few choices:
- You can always add some extra physical ram, this may help but may not get you to the root of the problem.
- You could maybe add a processor or two and hope for the best, or you can figure out why your ECM server is running so slowly.
There are several different things that can cause ECM system performance degradation. In this article we will explain how you can use Performance Monitor aka “PerfMon” a Microsoft Windows built in diagnostic tool to help determine the cause of your ECM server’s bottle neck.
As with any other diagnostic tool Performance Monitor is a running process and like any other process, Performance Monitor may consume things like CPU cycles, system memory, and potentially hard disk resources. This will slightly lower the amount of available system resources reported by Performance Monitor then when performance monitor is not running. Even with that Performance Monitor is still accurate enough that it can be used to help IT staff determine system bottle necks that are causing performance related issues. Continue reading