Author Topic: Troubleshooting - OnDemand Client or Content Navigator Desktop  (Read 117 times)

tjspencer2

  • Jr. Member
  • **
  • Posts: 77
    • View Profile
Troubleshooting - OnDemand Client or Content Navigator Desktop
« on: December 03, 2020, 11:09:28 AM »
I have an issue with many PDF documents I'm storing in CMOD - many have are documents with LOTS of images.

When my internal customers try to return some of these via Navigator, they can compromise my Navigator WebSphere app server on which I'm also running web services for external customer portal access  :( .

What I've had to do to help my external clients become whole is to stop the Navigator application in WebSphere to let the web services calls stabilize.

After some time passes I restart the Navigator process.

My question is, what if for these customers needing to access the large statements if I installed OnDemand Client on their desktops, would that resolve my problem?

I'm not sure if the problem is Content Navigator's communication with the CMOD Library Server OR if it's the process of converting PDF files and resources on the server to render the statement to the customer.

Also, is there a way to put a governor on the Conent Navigator destop to set a threshold on how large a file a user can retrieve through Navigator?







Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1007
    • View Profile
Re: Troubleshooting - OnDemand Client or Content Navigator Desktop
« Reply #1 on: December 03, 2020, 02:40:07 PM »
Quote
My question is, what if for these customers needing to access the large statements if I installed OnDemand Client on their desktops, would that resolve my problem?

Doing a test by installing the CMOD Windows Thick Client is certainly easy enough to do, so go ahead and give it a whirl.

Ed Arnold
#zOS #ODF

tjspencer2

  • Jr. Member
  • **
  • Posts: 77
    • View Profile
Re: Troubleshooting - OnDemand Client or Content Navigator Desktop
« Reply #2 on: December 04, 2020, 08:14:37 AM »
Ed - Thanks for the follow-up.

I can definitely birddog this and do some benchmarking.

Is there a way in Navigator to restrict content by size so that I can restrict viewing content i ONLY want viewed through OnDemand thick client?

I'm guessing the Navigator assumes if you've loaded it to a repository that you should be able to return it?

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1007
    • View Profile
Re: Troubleshooting - OnDemand Client or Content Navigator Desktop
« Reply #3 on: December 04, 2020, 12:31:28 PM »
For the record I'm completely Navigator illiterate --- hoping somebody else can jump in on this one.

Ed Arnold
#zOS #ODF

rjrussel

  • Jr. Member
  • **
  • Posts: 58
    • View Profile
Re: Troubleshooting - OnDemand Client or Content Navigator Desktop
« Reply #4 on: December 17, 2020, 09:14:04 AM »
You could potentially write a ICN plugin to do this. This assumes you have the size of the document stored as an index parameter. Otherwise you would have to retrieve the document to the ICN server, determine the size and then make a decision as to what to do with it. This not ideal at all though.