regerssion test with 2.4

we've been told to upgrade to 2.5 but I'd like to do a regression test first, just to make sure I have a valid starting point. The URL I had a year ago in my test harnes does not work any more.

In production, our application works unchanged for more than a year, connecting to https://api.pgiconnect.com/soap/sync with account AU/MORGSTAN We use the JobSubmit and JobDeliveryStatus interfaces

I'm looking for a test environment with the same version as production. We have a test account PT/TEST365 which used to work with https://xoa.pt.premiereglobal.com/soap/sync But now this URL returns Connection Refused. What would be the correct URL to use for a 2.4 test ? I repeat, this test is for regression, so I don't want to start upfront with 2.5. I need to make sure first that 2.4 works for me, before starting any upgrade.

A more fundamental question is whether any upgrade is necessary in the logic of my code. My application will be decommissioned by mid-year, so it could be a wasted effoert to develop any new logic.

Regards,

Andrew

Find more posts tagged with

Comments

skamens

You should not need to make any changes whatsoever in your application to use it with our system, even after the systemwide upgrade to 2.5. The software should be backwards compatible with your 2.4 code and schemas. If you are decommissioning your application soon, there should be no need for you to make any changes.

The URL you are using to access the PT system is still valid, and the PT/TEST365 account that you have been using is active, so you should be able to test against PT as you did before.

However, the API testing is migrating to a different system (test2), and I don't see that you have an account there. If you would like, I can arrange to have an account created for you on that system so you can verify your current application against the new software running in test2.

andrewsc

yes please, create an account for us on the test2 system. I presume that it runs the 2.5 version

The old system now works for me at https://xoa.pt.premiereglobal.com/soap/sync it was my bad, I forgot to update the proxy setting at my end.

From the email we got (attached) I gather will need to change the production URL, by end of March :

from: https://api.pgiconnect.com/soap/sync

to : https://myportal.easylink.com

A question about the dates. Is this new URL https://myportal.easylink.com already active in production ? Or is it still in a beta stage ? What would be the earliest date when we can switch over ? I'm not saying I'm eager to reconfigure my system, but there coulde be unrelated changes and I need to know the time-window available at your end.

easylink_notice.doc

sdik

The production API2.5 url is

https://messaging.easylink.com/soap/sync

https://myportal.easylink.com is our online portal for submitting jobs, checking job status as well as creating templates and performing list maintenance.

You can also use myportal to check on jobs you submitted via the API (your API credentials can be used to login to myportal).

Both links are active and are available for use.

skamens

Actually, the above is not 100% accurate.

https://myportal.easylink.com (the portal) is active and available, and is not expected to change.

The production URL for API 2.5 will be https://messaging.easylink.com/soap/sync, but it isn't there yet. Right now, this URL is running API 2.4.

If you wanted to access the 2.5 software in production befrore the changeover, you could use https://advancemessaging.easylink.com.

But for your purposes, where you really just want to keep using 2.4, you can changeover to https://messaging.easylink.com/soap/sync at any time between now and the end of March.

skamens

Oh, by the way - I did create an account for you in test2 - the user ID is "T2/TEST365", and it has the same password as the PT account.

You should be able to log into the portal in test2 (https://test2.myportal.easylink.com/welcome.do) to do any maintenance you need to do, or to look at your job statuses.

If there are any specific profile settings you need for this new account, please reach out to your account team.