Jump to content


mikelandl

Member Since 14 Sep 2005
Offline Last Active Jul 22 2016 02:36 PM
-----

Posts I've Made

In Topic: RESTFul Web Services - Internal Server Error: 500

20 May 2016 - 01:09 PM

Hi Matthews,

 

We were also having issues and ProIV support sent me the following which helped us.

 

This is an issue we have found that occurs when 8.2 is installed as an upgrade. There are a few lines that are missing from the web.xml.

 

 

Please add the following and restart the service:

 

 

<servlet>

 

<servlet-name>SwaggerCodeGenerator</servlet-name>

 

<servlet-class>com.northgateis.proiv.ws.rest.servlet.GeneratorServlet</servlet-class>

 

<load-on-startup>2</load-on-startup>

 

</servlet>

 

<servlet>

 

<servlet-name>RSDStorage</servlet-name>

 

<servlet-class>com.northgateis.proiv.ws.rest.servlet.RSDStorageServlet</servlet-class>

 

<load-on-startup>1</load-on-startup>

 

</servlet>

 

<servlet>

 

<servlet-name>ExportServlet</servlet-name>

 

<servlet-class>com.northgateis.proiv.ws.rest.servlet.ExportServlet</servlet-class>

 

</servlet>

 

<servlet>

 

<servlet-name>ImportServlet</servlet-name>

 

<servlet-class>com.northgateis.proiv.ws.rest.servlet.ImportServlet</servlet-class>

 

</servlet>

 

 

<servlet-mapping>

 

<servlet-name>RSDStorage</servlet-name>

 

<url-pattern>/rsd</url-pattern>

 

</servlet-mapping>

 

<servlet-mapping>

 

<servlet-name>SwaggerCodeGenerator</servlet-name>

 

<url-pattern>/codegen</url-pattern>

 

</servlet-mapping>

 

<servlet-mapping>

 

<servlet-name>ExportServlet</servlet-name>

 

<url-pattern>/export/*</url-pattern>

 

</servlet-mapping> /Swagger

 

<servlet-mapping>

 

<servlet-name>ImportServlet</servlet-name>

 

<url-pattern>/import</url-pattern>

 

</servlet-mapping> 


In Topic: How do you create a memory file?

23 November 2015 - 07:39 PM

Thanks Ross, that makes sense, although I must admit I was hoping for slightly better results!  :lol:

Do you have much experience with memory-based sort files? If so have you noticed substantial results with those?

Thanks.


In Topic: Open Client text alignment

04 December 2014 - 08:15 PM

What font are you using in the Windows Client - proportional e.g TimesNewRoman or fixed e.g CourierNew.

 

It sounds like you are using some sort of fixed font. If so you can amend you application CSS (that overrides the OpenClient CSS) and set the font to that employed in your Windows client settings.

 

Sorry, I should have replied to this earlier. ProIV showed me that using the CSS file in the PROIVClient folder in appResources will cause the open client to mimic (as well as possible) the MFC Client. While it doesn't look as nice as the default open client CSS file it does solve our immediate issue and gives us something to build from.


In Topic: Open Client text alignment

18 November 2014 - 02:06 PM

You can try splitting up the static text into 2 parts. take out the : from each line, and add new static texts lines with just the : and the row/column you want them to appear. that should align them out

 

Thanks Wim. I imagine that would work but unfortunately the work involved would be considerable.


In Topic: commit points

21 January 2014 - 07:12 PM

 

Mike,

 

Don't forget that proiv lock logic doesn't work with postgresql so any lock will result in a spinning session until the lock owner releases. NG were going to look into handling this but no news yet.

I ended up having to use a pro-isam lock file where I really need critical tables to be managed properly.

Doing this also has the advantage that you only have to 'B' mode the pro-isam file with the keys and the lock logic gives you an opportunity for the user to respond to the lock or a timed/count retry prior to any table access. The pro-isam file can double as an audit as Neil B has suggested.

 

 By using this method iscollect will clean up the pro-isam lock on a session failure no need for user/admin lock screens etc. 

 

Hi Neil,

 

ProIV just showed me something that can be added to your login script to get lock logic working. If you add "POSTGRESQL_NOWAIT=Y" to your login script lock logic works (at least from what I have been able to test so far). I don't see mention of this anywhere in the documentation so I've asked them to fill  me in as to what this actually does. I'll let you know once I hear back from them.

 

 

Please disregard, I jumped the gun on this one. Setting this option will essentially dself the record if a lock is encountered, which is not what we want in 99% of our functions.