SalesForce Connector

-
To provide IBM Support with sufficient information to debug a problem with SalesForce Connector, the following are the minimal collection requirements that should be provided:
  1. The exported job
  2. Director log
  3. Debugging Directory
Use the following commands to gather and generate the files described above.



Windows, AIX, Solarix, Linux, or HP-UX
Commands
Description
The Designer allows a job (such as a failing job) to be exported to a .dsx file. This can be imported by IBM Support to help understand the problem or reproduce it.
Specify the name of the file to be produced when you export the job.
The exported Job
Use the Director's log print dialog to produce a file containing the log of the failing job.
Specify the name of the file to be produced when you print the log.
Specify the "detailed" option in the print dialog.		The Director log
If a job fails consistently, and you are able to edit the job, collect a Debugging directory for the job. To create this directory:
  • Set the environment variables:  DS_PXDEBUG=1
     APT_DUMP_SCORE=1
  • Re-run the job. A directory will be produced in <IS_HOME>/<project>/Debugging/<job name>
Debugging Directory

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more