redhatworkshops / fusev7-workshop Goto Github PK

For the April 9 training ONLY

There seems to be a security vulnerability in one of the dependencies referenced here

https://github.com/RedHatWorkshops/fusev7-workshop/blob/master/slides/package.json

@sigreen You had last commit on this, but I know the BU overtook this. If you can take a look (or assign someone else) that'd be great

I've logged into the OpenTLC lab environment as stipulated by the setup instructions. Step 6 specifies I must select the "Fuse Ignite (OCP environment)" image, but unfortunately the image does not exist. Is this an issue with my account, or do I need to select another image?

Ask us to reuse the integration from Lab 2, but for house keeping, they have already delete all the integration at the end of lab.

This use case sees a custom step implemented using a static technical extension.
Choice of technical extension - a simple POJO that performs message logging.

For hosting Maven artifacts, I suggest the use of this Nexus Repo Manager - http://nexus-ocp-workshop.apps.589e.openshift.opentlc.com

Current screenshot within the lab does not reflect this warning. Is this a valid concern raised by Fuse Ignite?

Recommend that maven repositories are added to the pom.xml file of this project
https://github.com/RedHatWorkshops/fusev7-workshop/tree/master/labs/50-artifacts/project/migrated/claimdemo

Need help in creating an archetype, which is :
io.syndesis.extension
artifactId: extension-bom
version: 1.3.4

Repeated and contradictory property version numbers in solution pom.xml

The SQL properties of the Camel route are described to be filled with the following value

• Direct URI as direct:database
• SQL URI as sql:select name from information_schema.users?dataSource=#myCamelDS
• Log message as ${body}
• setBody Expression as Hello ${body[0][NAME]} and Language as simple

They should be replaced by these values:

• Direct URI as direct:database
• SQL URI as sql:sql:select returnname from nametable where nameno=${header.dbno}?dataSource=#myCamelDS
• Log message as ${body}
• setBody Expression as Hello ${body[0][RETURNNAME]} and Language as simple

Use case involving the "re-use" of Camel EIPs (implemented as Java Apps) as technical extensions.
Lab will see these technical extensions setup and used as Camel EIPs within Fuse Ignite integrations.
Use Aggregation and Splitter EIPs - cause they are mighty popular.

Recommend this Use Case (4) be combined with Use Case 1 (POJO technical extension)

The correct term is "recurring" payment. Throughout this lab, we see the use of "reoccurring" which is confusing lab participants

If we choose NOT to follow the optional activities, it's not clear where we can start the activity. Is it step 5?

The images on which links labs/71-management-and-monitoring.md are missing

the amq.queueName is missing

Line 6 should instead read --
host: water-company-tp3demo.4b63.pro-ap-southeast-2.openshiftapps.com

Using the popular shapeless connectors, Slack and Dropbox, in a single integration.
Use case involves message persistence to Dropbox, triggered by the arrival of a Slack message in a channel.
Recommend this Use Case (3) be combined with Use Case 2 (Data Mapper)

When the route is created, it doesn't connect itself to the service. You have to blow away the route and recreate it.

Schema data, from 2 or more REST services, are aggregated into a common data set - using the Data Mapper in Fuse Ignite.

https://gist.github.com/honghuac/d3d32e9488e5942d12ba273cdb4c6755

When you paste in the @Bean/@Autowired info, need to make sure the user picks springframework packages vs the camel packages.

should replace this image.