PxPlus User Forum

Twitter Twitter Twitter

Recent Posts

Pages: 1 ... 7 8 [9] 10
81
ODBC / Re: Serius I complete missing undesrtand odbc
« Last post by Mike King on February 21, 2024, 08:00:11 AM »
Edias is correct.  This appears to be the ProvideX ODBC driver as sold and supported by Sage with their MAS90 accounting package. 

If the issues you are having are relative accessing MAS90 data you should contact Sage for assistance as their ODBC driver is different than the drivers for PxPlus.
82
ODBC / Re: Serius I complete missing undesrtand odbc
« Last post by EVa on February 21, 2024, 03:06:40 AM »
For starters, you could enable debugging to see if there's a difference the 1st and 2nd time you connect.  Also, this appears to be a rather old version of the ODBC driver as it says 'ProvideX' in the title bar ?
83
ODBC / ODBC output from UPS Worldship
« Last post by dalem on February 20, 2024, 05:16:49 PM »
Any help or insight into this is appreciated!
on the off-chance the ( ?, ?, ?, ?, ?, ?, ?) in the error refers to UPS not being able to find it's own fields linked to ours in a writable PX+ file, I went in and re-did the mapping to make sure.

using 32 byte version of both ups & px+ odbc 5.2. Since the only similar error was responded with "why such an old version", its more of a decision above me.

This is the px+ driver log from the ODbc. The attached picture is what the UPS software and/or driver pops up with.
\\mcvan-app01\E\Share\CSV_FILES\UPS_EXPORT\UPS_EXPORT.ini , available 3 table(s)
<UPS_EXPORT1> Open file e:\SHARE\CSV_FILES\UPS_EXPORT\EXPORT_UPS_TO_JMAS, maxksz=47
ISAMCloseTable: Closing table UPS_EXPORT1 - 0 file reads, 0 re-reads, 0 writes, 0 removes
     CACHE STATS - 0 reads, size 9216 estimated, 0 used
ISAMClose
Driver version: 5.20.0000
ISAMOpen: UserID='cai-support', length=11
ISAMOpen: Trying to access the server using UserID='cai-support', Company=''
------------------------------
INSERT INTO UPS_EXPORT1 (TRACKING_NUMBER, WEIGHT, DOCUMENT_NUMBER, PKG_REFERENCE_1, USPS_WEIGHT, ORDER, SHMT_VOID_INDICATOR)  VALUES ( ?, ?, ?, ?, ?, ?, ?)

ISAMClose: <3> S0000 S0000 [PxPlus][ODBC Driver][FILEIO]Not supported
84
Programming / Re: Sign XML Documents with Digital Signatures
« Last post by HendersonS on February 20, 2024, 04:47:02 PM »
Thanks Mike for your instructions.

If I understood correctly, you mean that I can invoke this tool from pxplus? And just in case I take another route to do it with pxplus, is there any utility to extract the private key from a .pem?
85
ODBC / Re: slowing down an ODBC query
« Last post by Jeffrey Ferreira on February 20, 2024, 04:22:11 PM »
Thank you Devon. i will ask the customer if they would be partial to the Dirty Read.
86
ODBC / Re: slowing down an ODBC query
« Last post by Devon Austen on February 20, 2024, 03:29:31 PM »
The PxPlus SQL ODBC driver has some options that may help.

Goto the Options tab of the DSN setup page for the PxPlus ODBC client install. There you will find two options that may help.

Dirty Read - Check box for Dirty Read mode of operation to skip the normal file consistency checks.

                   Dirty reads can speed file processing by reducing the number of locks issued against a file. However, this may result in inconsistent data should the file be updated while being read by
                   the PxPlus SQL ODBC Driver.

Burst mode - Check box to enable Burst mode. This helps reduce some of the overhead created by temporary locks.

                      With Burst mode set, the PxPlus SQL ODBC Driver locks the file header for either 50 file operations or three-tenths of a second, whichever occurs first. This decreases the number of
                      times the file must be locked and the number of times that internal buffers may need to be reloaded. Refer to the next paragraph below for an explanation on the effect of temporary
                      locks.

I suspect dirty reads may be of the most help to you.
87
ODBC / slowing down an ODBC query
« Last post by Jeffrey Ferreira on February 20, 2024, 11:31:43 AM »
Hi All,

we are having an issue whereby when a user does a power bi query against our pxplus data via odbc it really can slow down performance for everyone else. Does anyone know of a way i can slow down/throttle pxpiosrv. Or maybe some other solution.

Jeff
88
Programming / Re: Sign XML Documents with Digital Signatures
« Last post by Mike King on February 20, 2024, 07:42:33 AM »
I would probably use XMLSEC (xmlsec1) to do this from command line as it is available on both windows and Linux and there is fairly extensive documentation available at:

http://sgros.blogspot.com/2013/01/signing-xml-document-using-xmlsec1.html

Here is the command documentation:

https://www.mankier.com/1/xmlsec1

While PxPlus logic could be used directly; by using a standard package like xmlsec1, should you have any issues the company receiving the XML may have examples.
89
Programming / Re: Sign XML Documents with Digital Signatures
« Last post by HendersonS on February 19, 2024, 08:23:19 PM »
Loren thanks for yor reply

Below is the structure that the signature node should have within the xml, I have no experience in building these signatures. Maybe you can show me some example code to do it.

Code: [Select]
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
 <SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/RECxml-c14n-20010315" />
<SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsigmore#rsa-sha256" />
<Reference URI="">
 <Transforms>
 <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#envelope d-signature" />
 </Transforms>
 <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256" />
 <DigestValue>Atr9H7DiGlxrQOFII/hFihsL6ACiwe47Oo93tgtuera=</DigestValue>
</Reference>
</SignedInfo>
 <SignatureValue>gQyXO0FFDGIITESTpP5xZjLIRtv/Q7/ixe1lNDLDA5aw...</SignatureValue>
<KeyInfo>
 <X509Data>
<X509Certificate>DGIITESTBFagAwIBAgIIInYGQUX9q0IwDQYJKoZIhvcNAQ...</X509Certificate>
 </X509Data>
 </KeyInfo>
</Signature>
90
Programming / Re: Sign XML Documents with Digital Signatures
« Last post by Loren Doornek on February 19, 2024, 12:57:33 PM »
You can do this in PXPlus using the HSH() function, and possibly the CVS() function to convert to Base64. 

I've worked on several web interfaces that require some sort of digital signature as part of the data (usually, as part of the HTTP data sent).  They are all very similar:  Take some chunk of data or a concatenation of various data fields, create a hash of that data using the private key, convert the hashed value to base64, then include the hashed value (signature) in the data being submitted.

The recipient also needs to know the public key which needs to be used to decrypt the signature.  In looking over the XML signing documentation, it appears that you must include the public key as a field in the XML data.  (For websites, you generally provide some sort of username/login, which the website then uses internally to retrieve the decryption key associated with your account)

The HSH function in PXPlus will allow you to encrypt the data in various formats using various keys (certificates) (https://manual.pvxplus.com/PXPLUS/functions/hsh.htm#format_1)

The CVS function can be used to convert the signature to base64 encoding (eg:  sig$=CVS(mydata$,"ASCII:BASE64")  ), or you can use the *web/base64 utility.

If you aren't able to get it working, let me know and I can try to generate a short example.
Pages: 1 ... 7 8 [9] 10