Giter Club home page Giter Club logo

apibusinesshub-integration-recipes's People

Contributors

aadinigam avatar amritalaxmi avatar annemariekiefer avatar bhalchandrasw avatar btbernard avatar codebude avatar kamleshzanje avatar maheshsrikrishnan avatar mandy-siu avatar mayurmohan avatar meghnashishodiya avatar mvernicek avatar sapapibusinesshub avatar sebastianwolf-sap avatar shilpavij123 avatar simplykapoor avatar srutisagaram avatar ssdhello123 avatar stefanboller avatar swalaskar avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

apibusinesshub-integration-recipes's Issues

Store Integration Artifact CICD Recipe

Hi Team,
I have been trying the integration recipes for CICD using Jenkins and Git Hub and facing the following issue:

java.lang.NoSuchMethodError: No such DSL method 'readJSON' found among steps [archive, bat, build, catchError, checkout, deleteDir, dir, echo, emailext, emailextrecipients, envVarsForTool, error, fileExists, findBuildScans, getContext, git, gitPush, githubNotify, httpRequest, input, isUnix, junit, library, libraryResource, load, mail, milestone, node, parallel, powershell, properties, publishChecks, pwd, pwsh, readFile, readTrusted, resolveScm, retry, script, setGitHubPullRequestStatus, sh, sleep, stage, stash, step, timeout, timestamps, tm, tool, unarchive, unstable, unstash, validateDeclarativePipeline, waitUntil, warnError, withChecks, withContext, withCredentials, withEnv, withGradle, wrap, writeFile, ws] or symbols [GitUsernamePassword, Number, Open, all, allBranchesSame, allOf, allowRunOnStatus, always, ant, antFromApache, antOutcome, antTarget, any, anyOf, apiToken, architecture, archiveArtifacts, artifactManager, asIsGITScm, authorizationMatrix, batchFile, bitbucketServer, booleanParam, branch, branchCreated, branches, brokenBuildSuspects, brokenTestsSuspects, buildButton, buildDiscarder, buildDiscarders, buildRetention, buildUser, buildingTag, builtInNode, caseInsensitive, caseSensitive, certificate, changeRequest, changelog, changeset, checkoutToSubdirectory, choice, choiceParam, cleanWs, clock, close, command, commentPattern, commit, commitChanged, commitMessagePattern, configFile, configFileProvider, contributor, created, credentials, cron, crumb, culprits, default, defaultFolderConfiguration, defaultView, deleted, demand, description, developers, disableConcurrentBuilds, disableResume, downstream, dumb, durabilityHint, email-ext, envInject, envVars, envVarsFilter, environment, equals, executor, expression, extendedEmailPublisher, file, fileParam, filePath, fingerprint, fingerprints, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitBranchDiscovery, gitHub, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubEvents, gitHubExcludeArchivedRepositories, gitHubExcludeForkedRepositories, gitHubExcludePrivateRepositories, gitHubExcludePublicRepositories, gitHubForkDiscovery, gitHubIgnoreDraftPullRequestFilter, gitHubPRStatus, gitHubPlugin, gitHubPullRequestDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTopicsFilter, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, gitUsernamePassword, github, githubAccessToken, githubBranches, githubPRAddLabels, githubPRClosePublisher, githubPRComment, githubPRMessage, githubPRRemoveLabels, githubPRStatusPublisher, githubPlugin, githubProjectProperty, githubPullRequests, githubPush, globalConfigFiles, gradle, hashChanged, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, isRestartedRun, issueCommentTrigger, javadoc, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobBuildDiscarder, jobName, junitTestResultStorage, label, labels, labelsAdded, labelsExist, labelsNotExist, labelsPatternExists, labelsRemoved, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, legacy, legacySCM, list, local, location, logRotator, loggedInUsersCanDoAnything, mailer, masterBuild, maven, maven3Mojos, mavenErrors, mavenGlobalConfig, mavenMojos, mavenWarnings, message, modernSCM, myView, namedBranchesDifferent, noGITScm, node, nodeProperties, nodejs, nodejsci, nonInheriting, nonMergeable, none, not, organizationFolder, overrideIndexTriggers, paneStatus, parallelsAlwaysFailFast, parameters, password, pattern, permanent, pipeline, pipelineTriggers, plainText, plugin, pollSCM, preserveStashes, previous, projectNamingStrategy, proxy, pruneTags, pullRequest, pullRequestReview, pullRequests, queueItemAuthenticator, quietPeriod, rateLimit, rateLimitBuilds, recipients, requestor, resourceRoot, restriction, restrictions, retainOnlyVariables, run, runParam, sSHLauncher, schedule, scmRetryCount, scriptApproval, scriptApprovalLink, search, security, shell, simpleBuildDiscarder, skipDefaultCheckout, skipStagesAfterUnstable, slave, sourceRegexFilter, sourceWildcardFilter, ssh, sshPublicKey, sshUserPrivateKey, standard, status, statusOnPublisherError, string, stringParam, suppressAutomaticTriggering, suppressFolderAutomaticTriggering, swapSpace, tag, tags, teamSlugFilter, text, textParam, timestamper, timestamperConfig, timezone, tmpSpace, toolLocation, triggeredBy, unsecured, untrusted, upstream, upstreamDevelopers, userSeed, usernameColonPassword, usernamePassword, viewsTabBar, weather, withAnt, workspace, zip] or globals [currentBuild, env, params, pipeline, scm]
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:219)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:124)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:41)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:163)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:158)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:161)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:165)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:135)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:135)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at WorkflowScript.run(WorkflowScript:49)
at cps.transform(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)
at jdk.internal.reflect.GeneratedMethodAccessor119.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55)
at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45)
at jdk.internal.reflect.GeneratedMethodAccessor124.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:76)
at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
at jdk.internal.reflect.GeneratedMethodAccessor123.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:83)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:136)
at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:275)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:187)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:420)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:95)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:330)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:294)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:139)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Finished: FAILURE

Improve SAP SuccessFactors Employee Central Integration with Fidelity - Plan Number as externalized parameter

Is your feature request related to a problem? Please describe.
The iFlow uses the plan number as a constant in the message mapping.
This leaves no option but to edit the package and once the package is edited then further updates may not get applied to it.

Describe the solution you'd like
If this PlanNumber field is externalized as a parameter similar to CompanyCode, then iFlow becomes configurable for multiple plans.

Describe alternatives you've considered
The only alternative is to edit the iflow or copy the iflow and then edit to change the plan number in message mapping.

Additional context
image

Redis Adapter Deployment Failed at CPI Iflow

Hello Mayur,

Your blog and resources on Apache Camel Redis component as SAP Cloud Platform Integration Adapter are really helpful. I have followed all the steps as described. I was able to create .esa file and deploy it in SAP CPI tenant.

However, I am facing the issue to use it in iflow. Redis iflow is not getting deployed as I am getting the error shown below. It would be great help if you can guide to resolve it as early as possible. Thank you in advance for your help.
redis iflow deployment failed

Error Details

[CONTENT][CONTENT_DEPLOY][InstanceError] : {"message":"ERROR","childMessageInstances":[{"message":"EXCEPTION","parameters":["java.util.concurrent.TimeoutException"]},{"message":"UNRESOLVED","parameters":["(&(component=spring-redis)(objectClass=org.apache.camel.spi.ComponentResolver))"]}]}

Azure Blob Storage Adapter build failed due to: CMD validation failed

Describe the bug
I have the following error when building the Azure Blob Storage Adapter :

mvn clean install
[•••]
[INFO] --- com.sap.cloud.adk.build.archive:1.30.0:build (build-adapter) @ camel-azure ---
[INFO] Path of the adapter to be built: /Users/i303934/SAPDevelop/Projects/PS/apibusinesshub-integration-recipes/Recipes/for/azure-integration-adapter/Project-Source/camel-azure
[ERROR] Attribute 'gen:RuntimeComponentBaseUri' value is not consistent with URI scheme
[ERROR] Attribute 'gen:RuntimeComponentBaseUri' value is not consistent with URI scheme
[ERROR] Adapter build failed due to: CMD validation failed

Expected behavior
The build should be successful

Desktop (please complete the following information):

  • OS: macOS Big Sur 11.5.2
  • Java Version
openjdk version "11.0.11" 2021-04-20 LTS
OpenJDK Runtime Environment SapMachine (build 11.0.11+9-LTS-sapmachine)
OpenJDK 64-Bit Server VM SapMachine (build 11.0.11+9-LTS-sapmachine, mixed mode)

Redis Adapter: Connection Refused

Hi @mayurmohan,

I am trying to connect on BTP Redis with CPI and Redis Integration Adapter imported following the guide.
I am receiving the following issue:

org.springframework.data.redis.RedisConnectionFailureException: Cannot get Jedis connection; nested exception is redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool, cause: java.net.ConnectException: Connection refused (Connection refused) (local port 58822 to address 10.128.14.130 (68531b95-e2c3-4f07-5fd9-557f), remote port 1287 to address 10.16.155.124 (ip-10-16-155-124.eu-central-1.compute.internal))

Please do you have any idea?
image

Thanks in advance.

I am unable to import .esa adapter to CPI cf

Hello,
I want to ask how to import custom adapter into CPI tenant. According to the documentation I should see there a an option to Add -> Integration Adapter but it is missing.

image
I am also assigned into groups AuthGroup.Administrator, AuthGroup.IntegrationDeveloper, AuthGroup.BusinessExpert and ESBMessaging.send.

If anyone could point me in the direction how to import .esa files into CPI I would appreciate it very much.

SSN Field issue for "SAP SuccessFactors Employee Central Integration with Fidelity"

Describe the bug
The iFlow produces an output which can have incorrect SSN values for the employees if the some of the employees in the selected dataset are having blank values coming from SF. If one of the employee has a blank SSN value then in the output the employee gets the next employee's SSN value assigned which potentially is a serious issue but as SSN is a key field for Fidelity it is less likely that this issue will happen in clean datasets of Pre-Prod/ Prod where every employee has valid SSN maintained. We noticed this issue in our Dev environment where test employees are not set up with full data set with valid SSN etc.

To Reproduce
Steps to reproduce the behavior:

  1. Go to SuccessFactors and create 3 new hire records i.e. create 3 new employees
  2. Maintain the national id record with country usa and correct value for SSN field for the first and third employee record
  3. Do not maintain the national id record for second employee so that SSN stays blank. It is not mandatory field in SF.
  4. Configure the pre-build package "SAP SuccessFactors Employee Central Integration with Fidelity" for SF connections etc.
  5. Run the iFlow to get the output file
  6. The file will show correct SSN for first employee, Incorrect SSN for second employee (assigns third employee's SSN to second employee), Blank SSN for the third employee

Expected behavior
Each employee must be assigned with correct SSN value from the employee data record from SF

Screenshots
SF Data
Employee 1234 SSN 123-45-6789
Employee 2345 SSN BLANK
Employee 3456 SSN 234-56-7890

File Output for 02E (partial record):
Plan SSN Record
XXXX 123-45-6789 02E1234
XXXX 234-56-7890 02E2345
XXXX 02E3456

Expected Output:
Plan SSN Record
XXXX 123-45-6789 02E1234
XXXX 02E2345
XXXX 234-56-7890 02E3456

Desktop (please complete the following information):

  • OS: Windows
  • Browser: Edge
  • Version: 123

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.
image

How can we call a custom defined Camel Processor in the Integration Flow?

Discussed in #74

Originally posted by sunil-solace April 9, 2023
We have a custom Camel based Adapter being developed. It basically invokes the Producer and Consumer implementations we've defined using Receiver and Sender, but we also would like to invoke a custom Processor in our Adapter from the Integration Suite. Is this supported, if yes, then what's the way around it?

Following is the example of what is being done:

The following processor is implemented in the Custom Adapter:

public class MyCustomProcessor implements Processor {
  @Override
  public void process(Exchange exchange) throws Exception {
    //...
  }
}

and this is how it would work in the Camel world:

<bean id="myCustomProcessor" class="com.example.MyCustomAdapter.MyProcessor"/>

  <camelContext>
    <route>
      <from uri="direct:start"/>
      <process ref="myCustomProcessor"/>
      <to uri="mock:result"/>
    </route>
  </camelContext>
</beans>
```</div>

Configuration Parameter Error - for /sapsuccessfactorsemployeecentralwiththirdpartypayrollvendor/

Describe the bug
The configuration for "SAP SuccessFactors Employee Central with Third-Party Payroll Vendor- Template A" mentions the "FileName" parameter for the PayrollFile Receiver and documentation mentions that it applies to all 3 SFTP connectors. However, the file name mentioned applies only to Terminations file and remaining 2 file outputs (Daily changes, Hirerehire) are not configured for the provided file name resulting the iFlow in error after deployment.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Configure' and Provide FileName for the PayrollFile Receiver
  2. Click on 'Deploy'
  3. Scroll down to 'Start' or 'SFTP'
  4. See error - FileName is not valid, no such file

Expected behavior
The File Name configured should apply to all 3 SFTP channels but 2 channels remain unconfigured for "FileName"
If we edit the iFlow to correct this then we will loose on the updates

Screenshots
image

image

image

image

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows 10
  • Browser [e.g. chrome, safari] Edge
  • Version [e.g. 22] Version 114.0.1823.79 (Official build) (64-bit)

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

mongodb-integration-adapter

According the following blog, I have 3 questions:
https://blogs.sap.com/2020/07/23/connecting-to-mongodb-server-from-sap-cloud-platform-integration-using-camel-mongodb-component/

First question :
That mean that the connection to the Mongodb database is hard coded in the adapter ?
So, if I have 3 databases dev, test Prod, I need 3 adapters.

Second question :
My database need a user and password.
So I have to to use something like that : mongodb://username:password@localhost/mydb
Is it correct ? that mean that my user/password are also hard coded. Is there a security risk there ?

Third question :
My database is on premise. So, I guess I need to use the cloud connector. how do it interface with the adapter ?

Regards,
Shay

Issue with "GoLiveDate" external parameter for SAP SuccessFactors Employee Central with Third-Party Payroll Vendor

Describe the bug
The configuration parameter "GoLiveDate" is not taken into account in the "payrollProcessingLogic.gsh". The Script is looking for the "ADPGoLiveDate" (old?) parameter. This results in the iFlow in deployment error as below-
Error Details
javax.script.ScriptException: java.lang.Exception: java.lang.NullPointerException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable 'text'@ line 16 in payrollProcessingLogic.gsh, cause: java.lang.NullPointerException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable 'text'

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'SAP SuccessFactors Employee Central with Third-Party Payroll Vendor'
  2. Click on 'Configure the iFlow with parameters for SuccessFactors and SFTP details'
  3. Deploy the iFlow
  4. See error

Expected behavior
With all required configurable parameters provided, there should not be any deployment error.

Screenshots
image

image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Edge/ Chrome
  • Version 115/115

Additional context
This just might be the reference to old ADP based variables, as this package is now generalized for any payroll providers.

Is there a support for Map datatype in the Component Metadata for Custom Adapters?

Discussed in #73

Originally posted by sunil-solace April 3, 2023
The idea is to be able to consume a Map (Key,Value) input from the user using the Component Metadata while building a Custom Adapter. This is a useful feature for initializing connections with custom properties which gives greater control to the end-user rather than defining each of those properties a separate input field.

How to

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Issue with Bundesanzeiger Integration with SAP S4HANA GTS OnPremise

I have an issue with the iflow "Query and send SanctionsLists from Bundesanzeiger to SAP S4HANA GTS" in package "Bundesanzeiger Integration with SAP S/4HANA GTS OnPremise".

after configuration according to the Guide "https://github.com/SAP/apibusinesshub-integration-recipes/blob/master/Recipes/for/bundesanzeigerintegrationwithsaps4hanagtsonpremise/IntegrationBundesanzeigerandGTSviaCPI.pdf" I'm getting the following error:

org.apache.camel.component.ahc.AhcOperationFailedException: HTTP operation failed invoking https://www.awr-portal.de/SubDi/index.jsp?user=XXX&pass=XXX&path=SAPschnittstelle/XML(gts)/Sanktionsliste with statusCode: 404

So, something seems to be wrong with the URL path. Can you provide with the correct details?

Thanks and best regards!
Christopher

Error with SAP Ariba Integration Toolkit - SAP Ariba Integration File Upload Events - Buying

Hello,
We are facing an issue with this iFlow every time we have more than one file to upload to ARIBA. The first one goes well, but the second failed with this error: Throwable caught: Task CombinedDataPull already running. || No stack available (HTTP 503)
I've noticed that the SFTP sender adapter is configured to get just one file per poll, but our CPI tenant has two runtime nodes, so two parallel processes are fired every time. (you can verify this behavior at https://help.sap.com/docs/cloud-integration/sap-cloud-integration/configure-sftp-sender-adapter, "Max. Messages per Poll" parameter)

Is there something we can do to solve this issue?
Thank you in advance.

Adrián

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.