ILINX Content Store Upgrade in Less Than 5 Minutes!

Pressed for time I just watched one of our system engineers upgrade a production ILINX Content Store in less than 5 minutes. An amazing feat for an Enterprise Content Management System!

From the ILINX Installation Guide:
  1. Run the new ILINX installation package.
      UPDATE CONFIGURATION FILES
  2. Browse to and open: [installation folder]ImageSourceILINXWCFWeb.config
    • Modify it by doing the following.
    • From the backed-up Web.config file, copy the following section.
    • Paste into the new Web.config file.
  3. Browse to and open: [installation folder]ImageSourceILINXImportContentWindowsService.exe.config
    • Modify it by doing the following:
      • From the backed-up ImportContentWindowsService.exe.config file, copy the following line
      • Paste into the new ImportContentWindowsService.exe.config file.
  4. Browse to and open: [installation folder]ImageSourceILINXWebClientApplication FilesILINX_ILINX.exe.config.deploy
    • Modify the endpoint values with the correct URL.
    • From the backed-up ILINX.exe.config.deploy file, copy the endpoint host value
    • Paste into the new ILINX.exe.config.deploy file MAGE UI
  5. Run mageui.exe to launch the Mage user interface.
    • This is located at:C:[Program Files directory]Microsoft SDKsWindowsv[X.X]Bin
    • NOTE: If installing on a Windows 7 or Windows Server 2008 system and the User Account Control (UAC) uses the default settings, be sure to run this tool as an Administrator. To do, right-click on the executable and select “Run as administrator”.
  6. Select File | Open and navigate to and Open:[installation folder]ImageSourceILINXWebClientApplication FilesILINX_<version>ILINX.exe.manifest
  7. Change the number in the “Version:” field to increment the last number by 1. As an example, if the Version number is 1.5.1.0, modify it to be 1.5.1.1. Note entered number here: __________________.
  8. Select Files in the left window pane, and ensure that the box is checked next to “When populating add the .deploy extension to any file that does not have it”.
  9. Click the Populate button, and select OK to the “Message: The operation will permanently add .deploy extensions…”
  10. Select File | Save
  11. From the displayed dialog box, sign the manifest file.

    A generic/unsigned certificate is included out of the box. It is important to use the customer’s own certificate when available. The following steps describe using the out of the box certificate. If an internal certificate exists, follow the same steps, but use the appropriate internal certificate and key during the signing process.

    • Select Sign with certificate file and click on the “” Browse button.
    • Navigate to and Open: [installation folder]ImageSourceILINXWebClientsigningKey.pfx
    • In the Password field enter ILINX. This is the password if using the out of the box certificate.
    • Select OK. Do not close the Mage program.
  12. Select File | Open and navigate to and Open:
    • [installation folder]ImageSourceILINXWebClientILINX.xbap
  13. Change the number in the “Version:” field to increment the last number by 1. Be sure to use the same number as entered in Step #5 above.
  14. Select Application Reference in the left window.
    • Click the Select Manifest… button.
    • Navigate to and Open: [installation folder]ImageSourceILINXWebClientApplication Files ILINX_<version>ILINX.exe.manifest.
    • Select File | Save
  15. From the displayed dialog box, sign the file
      A generic/unsigned certificate is included out of the box. It is important to use the customer’s own signing file when available.
      The following steps describe using the out of the box certificate.

    • Select Sign with certificate file and click on the “” Browse button.
    • Navigate to and Open: [installation folder]ImageSourceILINXWebClientsigningKey.pfx
    • In the Password field enter ILINX

    This is the password if using the out of the box certificate.

  16. Select OK and Exit the Mage program.

It’s that easy!

Mark Staley
Support Engineer
ImageSource, Inc.

mellerbeck - August 10, 2011

I’m not sure I would be too proud… there are some steps that could be automated! Any time I’m editing files I’m thinking the computer could do this for me…..

mellerbeck - August 10, 2011

I’m not sure I would be too proud… there are some steps that could be automated! Any time I’m editing files I’m thinking the computer could do this for me…..

Tracy Lim - August 10, 2011

By comparison traditional ECM would take hours if not weeks to install. Granted the process you mentioned could be automated but we are choosing to put resources into automating the processes that will yield significant time savings not a few minutes for one person once or twice a year. 🙂

Tracy Lim - August 10, 2011

By comparison traditional ECM would take hours if not weeks to install. Granted the process you mentioned could be automated but we are choosing to put resources into automating the processes that will yield significant time savings not a few minutes for one person once or twice a year. 🙂

Mike Peterson - September 2, 2011

But if we completely automate the process, we’re gonna put sysadmins out a job 😉 But I hear what you’re saying…you’re right, there are parts that could be automated. But the point was more in comparison to legacy imaging management systems that required much more involved procedures. Automation is coming!

Mike Peterson - September 2, 2011

But if we completely automate the process, we’re gonna put sysadmins out a job 😉 But I hear what you’re saying…you’re right, there are parts that could be automated. But the point was more in comparison to legacy imaging management systems that required much more involved procedures. Automation is coming!

Comments are closed