Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84539members
353793posts

Setting up the ETL client environment and "Spoon Client Library"

EcoStruxure IT forum

A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.

Solved
DCIM_Support
Picard
Picard
0 Likes
3
280

Setting up the ETL client environment and "Spoon Client Library"

This question was originally posted on DCIM Support by Akihiro Yamagami on 2018-09-13


I cloud not find the documents to setup the environment to develop custom transformation.
I took the following steps. Is this the appropriate procedure?

  1. Download pdi-ce-****.zip from SourceForge and unzipped.(data-integration folder is created)
  2. Download "Spoon Client Library" from webmin page and found "lib and plugins folders" in it.
  3. Copy these "lib and plugins folders" into "data-integration folder".

By the way, I'm developing custom transformation, but I still cannot understand the purpose of "Spoon Client Library".
I also found the DCO related steps, such as "DCO Cage Input" in the "design view" of Spoon, but I cloud not find the information how to use them.
Could you kindly explain the purpose of introducing "Spoon Client Library"?

Regards,

Akihiro Yamagami

(CID:134031147)


Accepted Solutions
DCIM_Support
Picard
Picard
0 Likes
1
280

Re: Setting up the ETL client environment and "Spoon Client Library"

This answer was originally posted on DCIM Support by Benjamin Bjørn Larsen on 2018-09-13


Hi Akihiro,

 

I must admit, I am unsure if we have any official documentation on how to interact with these custom steps.  However, I can give you a brief explanation.

 

In a few words:

The "Spoon Client Library" is a library, which exposes Pentaho Data Integration/Spoon/PDI transformation steps specific for Struxuware Data Center Operation (DCO), to the PDI client.

 

Some deeper insights:

The steps will give you, the designer of ETL integrations, a means to interact with the DCO server directly, utilising some of the functionality and computations, done internally in DCO.

By the nature of the transformation steps, they're "black box" steps, which doesn't give you any insight into their inner workings. They do connect to a counter part on the  DCO Server, which they'll be able to connect to. The data they're exposing can be found directly from the output of the standard export job.

When I am designing a ETL export integration, I've rarely used the steps my self (I can't think of when, if ever), I am instead usualy basing them on the output from the standard export job, whenever I need some of the data generated through these steps. I've found it easier to work with in a general context, than using the usage specific steps from the library. We do however provide you with the option to use the steps, if you'd prefer.

 

I hope this was the information you needed, otherwise I can try to find you some official documentation (if we have any) for you. 

 

Best regards,

Benjamin

(CID:134031629)

See Answer In Context

3 Replies 3
DCIM_Support
Picard
Picard
0 Likes
1
281

Re: Setting up the ETL client environment and "Spoon Client Library"

This answer was originally posted on DCIM Support by Benjamin Bjørn Larsen on 2018-09-13


Hi Akihiro,

 

I must admit, I am unsure if we have any official documentation on how to interact with these custom steps.  However, I can give you a brief explanation.

 

In a few words:

The "Spoon Client Library" is a library, which exposes Pentaho Data Integration/Spoon/PDI transformation steps specific for Struxuware Data Center Operation (DCO), to the PDI client.

 

Some deeper insights:

The steps will give you, the designer of ETL integrations, a means to interact with the DCO server directly, utilising some of the functionality and computations, done internally in DCO.

By the nature of the transformation steps, they're "black box" steps, which doesn't give you any insight into their inner workings. They do connect to a counter part on the  DCO Server, which they'll be able to connect to. The data they're exposing can be found directly from the output of the standard export job.

When I am designing a ETL export integration, I've rarely used the steps my self (I can't think of when, if ever), I am instead usualy basing them on the output from the standard export job, whenever I need some of the data generated through these steps. I've found it easier to work with in a general context, than using the usage specific steps from the library. We do however provide you with the option to use the steps, if you'd prefer.

 

I hope this was the information you needed, otherwise I can try to find you some official documentation (if we have any) for you. 

 

Best regards,

Benjamin

(CID:134031629)

DCIM_Support
Picard
Picard
0 Likes
0
280

Re: Setting up the ETL client environment and "Spoon Client Library"

This comment was originally posted on DCIM Support by Akihiro Yamagami on 2018-09-18


Thank you for your detail explanation. It's quite helpful to understand ETL.

I understand that the steps of "Spoon Client Library" are internally used for connecting DCO server and user don't need to care the steps in general.

I could already enough data in export database using standard export job, swoExportJob.

So, I will use this export job.

 

Best regards,

Akihiro Yamagami

(CID:134032985)

DCIM_Support
Picard
Picard
0 Likes
0
280

🔒 Closed

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.