Domain of a DR account submitted jobs

An API user in Japan is considering a DR account.
When Japan fax delivery system can not be used, the user plans to send requests to XSI.

Current JobSubmitRequest of the user has Domain set to "jp".
The question is, if s DR account is set up in XSI,
what Domain should the request contian that is sent to api.pgiconnect.com ?
Is it "xsi" or "jp" ?

Please advise what other considerations, if any, becomes necessary when API is used in DR setting.

Find more posts tagged with

Comments

skamens

In general, customers should not specify the "Domain" element in their input XML for the API.

The API will determine the appropriate domain to which a job should be submitted using the permitted domains from validate as well as the configuration specified through DSS (the Domain Selection Service).

So I would recommend that they not include "Domain" at all, and rather that you arrange to have them set up with an appropriate DR configuration through the ops group that handles that.

Shin Ishikawa

JobSubmit request works fine without domain in the request. Job delivery status query for submitted jobs specify Domain,Jobnumber pair and works ok too.

JobList request without domain returned list of fax jobs but also returned following error message:

<ErrorCode>2801</ErrorCode>
<ErrorMessage>[usmr2] Domain not available for this request </ErrorMessage></Error>

The job list request seemed looking for messageReach jobs. Is there any way to tell api that this user want fax job status only?

Attached run log is reproduction of the error message using house account XJI/TX/ASTEST1 which has DR configured with XSI.

API_DR_JobList.txt

skamens

Without a domain specification, JobList will attempt to reach out to all of the domains that are configured for a user (both XDDS and MR).

The error you received indicates that the user in question has usmr2 configured as an alternate domain, but the API installation you are using (jpxoa2app2) doesn't have configuration that tells it how to reach out to usmr2. But it is not a total failure of the request - we return the lists of jobs that we can get, along with the indication that we can't get data from that one.

There are a number of options to deal with this:

The JP XOA installation probably should be fixed to correct this. This can be done by configuring approrpriate connections between this system and the handlers on the usmr2 domain. INET SA can handle this.
INET SA could also configure the JP system to simply ignore the usmr2 domain. That's not my personal preference, because it doesn't allow folks to get status from usmr2, but it is possible.
The user could have their set of domains adjusted so usmr2 is not one of their possible domains.
The user can specify a domain of "XDDS" in the JobList request, which will cause us to only reach out to their XDDS domains. That would skip both MR domains.