CRM and CX Blogs by Members
Find insights on SAP customer relationship management and customer experience products in blog posts from community members. Post your own perspective today!
cancel
Showing results for 
Search instead for 
Did you mean: 
R_Zieschang
Contributor
11,131
Part I: Develop your first SAP Customer Checkout Plugin

In the first part of this five-part blog series we are going to develop our first SAP Customer Checkout plugin. We are going to learn how to setup our eclipse project, use the cco API and build our plugin. To deep dive into the development, there are some prerequisites:

  • Eclipse and Maven installed

  • some experience in Java

  • SAP Customer Checkout 2.0 FP06 PL02 (with B1 Integration) installed and configured


After you started your Eclipse, right click in the package explorer and we will create a new Maven Project. I’ll explain why we use maven later on.



Click Next in the „New Maven Project“-wizard until you reach the screen where we need to set the Group Id and the Artifact Id.



You can choose whatever namespace you want to use, just make sure it does not collide with any other java packages (e.g. use your surname in the namespace or your company). Click finish.

Eclipse will now create a structure for your plugin and also a pom.xml which will be used for external dependencies and also for the creation of the MANIFEST file. Open the pom.xml with a text editor (I strongly recommend using the Spring Web Flow XML Editor which is part of the Spring Tools Suite you install at the eclipse marketplace).

The pom.xml should look something like this.



We will make some changes to it. Within the <properties> Tag add the following new properties:
<sap.scco.pluginClass>com.be1eye.cco.blogpluginpart1.App</sap.scco.pluginClass>
<sap.scco.POSVersions>n/a, 2.0 FP06</sap.scco.POSVersions>

In the sap.scco.pluginClass enter your namespace (your groupId) followed by the pluginname (your artifactId) and followed by App which will be our main class Eclipse already created for us. In the second property sap.scco.POSVersion you can enter a list for all CCO Versions your plugin can is compatible to. In our case this is 2.0 FP06.

After that, we also need some instructions for maven, so that maven will build our plugin correctly. Just copy and paste this part right under the </dependencies> part.

 
<build>
  <resources>
    <resource>
      <directory>resources</directory>
    </resource>
  </resources>
  <plugins>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-shade-plugin</artifactId>
      <executions>
        <execution>
          <phase>package</phase>
          <goals>
            <goal>shade</goal>
          </goals>
          <configuration>
            <artifactSet>
              <excludes>
                <exclude>com.sap:scco:*</exclude>
              </excludes>
            </artifactSet>
<filters>
<filter>
<artifact>*:*</artifact>
<excludes>
<exclude>META-INF/*.SF</exclude>
<exclude>META-INF/*.DSA</exclude>
<exclude>META-INF/*.RSA</exclude>
</excludes>
</filter>
</filters>
<transformers>
<transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
<manifestEntries>
<PluginName>${project.name}</PluginName>
<CashdeskPOSPlugin>${sap.scco.pluginClass}</CashdeskPOSPlugin>
<CashDeskVersions>${sap.scco.POSVersions}</CashDeskVersions>
<Version>${project.version}</Version>
<Specification-Title>${project.name}</Specification-Title>
<Specification-Version>${project.artifact.selectedVersion.majorVersion}.${project.artifact.selectedVersion.minorVersion}</Specification-Version>
<Specification-Vendor> ${project.organization.name}</Specification-Vendor>
<Implementation-Title>${project.name}</Implementation-Title>
<Implementation-Version>${project.version}</Implementation-Version>
<Implementation-Vendor-Id>${project.groupId}</Implementation-Vendor-Id>
<Implementation-Vendor>${project.organization.name}</Implementation-Vendor>
<Implementation-URL>${project.url}</Implementation-URL>
</manifestEntries>
</transformer>
</transformers>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>


Your pom.xml now should look something like this:



These are classes to test your code but writing tests for our plugin is not scope of this blog series so we get rid of them.



Now we are going to add the ENV.jar of our SAP Customer Checkout Installation. Right Click your plugin name -> Build Path -> Configure Build Path...



Go to the tab Libraries and click on Add External JARs. Navigate to your SAP Customer Checkout installation and add the ENV.jar to your build path.



Click on Apply and Close. Now open the App.java file in your project.



Remove the static main method and extend the BasePlugin Class from SAP Customer Checkout.



Make sure you add the import afterwards. Just hover your mouse over BasePlugin and add the import.



Now we have to implement some methods so that SAP Customer Checkout knows how our plugin is called and which version it is. Just add these unimplemented methods by hover with your mouse over App and click add unimplemented methods.



You will see, that Eclipse has added 3 Methods getId(), getName() and getVersion().

Change the return values according your pluginid, name and version.



Notice the return value of the getVersion(). It will always output the version you set in your pom.xml.



Now we just have to build our plugin, copy it into the SAP Customer Checkout installation and we’ll see our first plugin running.

Right Click on our plugin folder -> Run as -> Maven Build…



Give this build configuration a name, set the goal to package, skip tests, apply and run. You should see the maven output in the bottom of your eclipse windows. If everything went well, you should see a folder named target. In this folder you will see a jar file with your artifactId and your version.



When successfull you can start the build from now on from eclipse directly.



Sometimes the build is failing, so please right click on your project -> Maven -> Update Project… and

update your project. The next build will be successfull eventually.

Copy the plugin jar file into the following folder [SAP Customer Checkout Installation folder]/cco/POSPlugins/AP



To be able to debug our plugin later, we need to add some parameters to the run.bat. So open run.bat with your prefered editor and search for the following part and the marked lines:



The first line will open a socket everytime Customer Checkout starts. The second line prevents cco from closing your browser everytime you restart or close cco.

Start your SAP Customer Checkout, log in and click on the cogwheel to open the CCO Backend. In the tab Plug-Ins you will now see, that our plugin successfully connected to Customer Checkout. Congratulations you just developed your first SAP Customer Checkout Plugin!



In the next part of this series, we will learn how to store and read our own plugin properties, how to write to the SAP Customer Checkout log and many more. So stay tuned!

If you have any questions do not hesitate to contact me.

 

The source is also hosted on gitlab: https://gitlab.com/ccoplugins/blogpluginpart1

 

Part II
24 Comments
bikash_bansal
Product and Topic Expert
Product and Topic Expert
Very good and detailed blog. Super Robert.
0 Kudos
Hi Robert,

Thank you for the blog.

Unfortunately, it does not work for me. Can you please suggest possible solution.

If a plugin for CCO was made without Maven, it works like charm.

After downloading your repository, this error appears:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project blogpluginpart1: Compilation failure

[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

A few strings have been added to pom.xml for fixing:

<plugin>

<artifactId>maven-compiler-plugin</artifactId>

<version>3.6.0</version>

<configuration>

<source>1.8</source>

<target>1.8</target>

<fork>true</fork>

<executable>C:\Program Files\Java\jdk1.8.0_121\bin\javac.exe</executable>

</configuration>

</plugin>

But as result new error:

 

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.0:compile (default-compile) on project blogpluginpart1: Compilation failure: Compilation failure:

[ERROR] C:\Projects\RTL\SAP_CCO\Maven_exp\src\main\java\com\be1eye\cco\blogpluginpart1\App.java:[3,29] error: package com.sap.scco.ap.plugin does not exist

 

ENV.jar has been added as external jar. Maven and Java JDK were installed.
R_Zieschang
Contributor
Hi Sergei,

 

I did not test the build with the maven compiler plugin. Maven normally uses the JAVA_HOME Environment Variable to discover it's JDK. Can you please check, if your JAVA_HOME Environment Variable points to your JDK?

Have a look at:
https://www.mkyong.com/java/how-to-set-java_home-on-windows-10/

Then try to remove the plugin you have added to your pom.

 

Alternatively you could also install the ENV.jar to your local maven repository (which I personally would prefer, but this was not in the scope of this blog).


It should work like that:

mvn install:install-file -Dfile=<path-to-ENV.jar> -DgroupId=com.sap -DartifactId=scco -Dversion=2.0_FP06_PL02 -Dpackaging=jar

(change -Dversion to the version of your ENV.jar)

After this you can add your ENV.jar to the maven dependencies like this:

<dependencies>
<dependency>
<groupId>com.sap</groupId>
<artifactId>scco</artifactId>
<version>2.0_FP06_PL02</version>
<scope>compile</scope>
</dependency>
</dependencies>

(Change version in the <version> Tag to the version you set with the mvn install command)

Then remove the the ENV.jar from your build path in eclipse. Maven should now automatically look for the ENV.jar in your local repository.

With this process you could easily install several ENV.jars with different versions to test your plugin with different CCO Versions.

 

Please let me know if this worked!

Regards
Robert

 
0 Kudos
Hi Robert,

Thank you very much for prompt reply. It is very helpful.

Maven for CCO works for me.

 

Only one thing, without  maven-compiler-plugin your example works, but my plugin shows errors:

 

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project rnz_plugin: Compilation failure

[ERROR] /…/Shared.java:[11,65] diamond operator is not supported in -source 1.5

[ERROR]   (use -source 7 or higher to enable diamond operator)

 

Which looks like Maven uses Java 1.5 in Eclipse for some reasons, at the same time installed Maven version shows:

 

Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-25T07:41:47+13:00)

Maven home: C:\dev\apache-maven-3.6.0\bin\..

Java version: 1.8.0_121, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_121\jre

 

The solution which works for me is adding code below in pom:

 

<plugin>

<artifactId>maven-compiler-plugin</artifactId>

<version>3.6.0</version>

<configuration>

<source>1.8</source>

<target>1.8</target>

</configuration>

</plugin>

 

And after that it works perfectly.

Please correct me if did something wrong.
R_Zieschang
Contributor
Hello Sergei,

 

many roads lead to rome. You did nothing wrong.

 

You could try to remove the compiler plugin and set the compiler target and source in the properties (where you set the sap.scco.pluginClass).

So it could look like this:

<!-- Properties -->
<properties>
<sap.scco.pluginClass>your.main.class.of.your.plugin</sap.scco.pluginClass>
<sap.scco.POSVersions>n/a, 2.0 FP06</sap.scco.POSVersions>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
</properties>

But I am happy, that this works for you. If you have any trouble do not hesitate to contact me.

Regards

Robert

 
0 Kudos

Hi Robert,

Thank you for advice. I’ve tried, it works and looks better than with additional plugin.


I have just one major issue with plugin development for CCO. It is API documentation. There quite a few examples, some learning introduction PDF, which are very helpful. However, it takes time to find appropriate class and method and there is no guarantee, that right way without side effects has been chosen.

For example, task1:
CCO should show modal message to user if barcode is not found.

Solution the task1:
@PluginAt(pluginClass=IBarcodeManager.class, method=”findAllByCodeCached”, where=POSITION.AFTER)
With
UIEventDispatcher.INSTANCE.dispatchAction(“SHOW_MESSAGE_DIALOG”, null,
dialogOptions);

It works fine, but with API docs it would much faster to find this. Also, BarcodeManager contains methods:
findAllByCodeCached(String)
findByCode(String)
findByCodeCached(String)
I found appropriate for my simple scenario with debuger, but I am not fully sure and do not know for what others.

Another task with weight barcodes (barcode contains item code and total amount), they are generated externaly, dynamically (depended on weight) and do not exist in database. I think in this case, MaterialEntity can be found manually using MaterialManager class. After that, I should add MaterialEntity and total to sale document…

CCO plugin development looks powerful, but quite time-consuming without API docs. Probably, I miss something.

 

Thanks a lot,

Sergei

R_Zieschang
Contributor

Hi Sergei,

I know that this is time consuming to find the right classes and methods which may fit your needs, but afaik there is no “real” API doc. But maybe gunther.sandtner2 knows more about this topic.

Regarding the barcode scan:

We already developped a plugin which may meet your requirements. Hit me up if you want to know more.

Regards

Robert

former_member237414
Contributor
zags1611 ,

the email adress is info@hokona.de .

Have a good day,

Julian
former_member609283
Participant
0 Kudos
Hi Robert,

Thank you for the blog,this is really helpful.

I am following your blog step by step but unfortunately,i am facing issues in POM.xml (Maven) and whenever i run the maven build following error message appears

Unknown lifecycle phase "Package". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]

Can you please suggest possible solutions for it or share any sample material for it.

Following is the my POM.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.be1eye.cco</groupId>
<artifactId>blogpluginpart1</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>
<name>blogpluginpart1</name>
<url>https://maven.apache.org</url>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<sap.scco.pluginClass>com.be1eye.cco.blogpluginpart1.App</sap.scco.pluginClass>
<sap.scco.POSVersions>n/a, 2.0 FP06</sap.scco.POSVersions>
</properties>
<build>
<resources>
<resource>
<directory>resources</directory>
</resource>
</resources>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>shade</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>

And can you please suggest a solution if we develop a plugin  in java eclipse without using apache maven that how can we  connect  plugin source code to customer checkout .
R_Zieschang
Contributor
0 Kudos
Hi Idrees,

there is a difference between "Package" and "package". This is why maven does not know what to do. Can you please tell me how you start the built?

Could you also please try to navigate in your folder where you put the plugin via commandline and type 'mvn package' and see if it works?

Please consider to have the mvn binaries added to your environment variables of your operating system.

 

Without maven open your Eclipse, right click on your plugin -> build path -> configure build path.In the tab libraries add an external jar. Choose the ENV.jar.

 

Regards

Robert
former_member609283
Participant
0 Kudos
Hi Robert,

Thanks for your kind reply.

As you described in your blog that Right click on the plugin folder > Run as > Maven build ,a wizard opens and in this wizard i mentioned Package as a goal and run the build but again i am facing same issue that Package lifecycle is not defined.

Yes,Maven environment variables added to operating system and command line runs successfully.
R_Zieschang
Contributor
0 Kudos
Hi Idrees,

 

please change then "Package" as goal to "package" in Eclipse like in my screenshot. Package is not a valid goal for the maven-shade-plugin.

 

If you want to build without maven (I would definitely recommend to go this way because it is way more convenient when working with external libraries) you also need to add a manifest file (which is automatically generated when you are using my maven example.

So add a Manifest File within the root of your plugin. It should look something like this:

Manifest-Version: 1.0
PluginName: [Name of your plugin]
CashdeskPOSPlugin: [namespace of your plugin]
CashDeskVersions: [versions for which your plugin is intended e.g. 2.0 FP07]
Version: 1.0

After this right click on your plugin, choose export -> Java -> Jar file -> select your plugin (choose all necessary files) -> select output destination -> in the JAR Manifest Specification choose your Manifest you just created -> Finish.

 

Regards

Robert
nsetab
Explorer
0 Kudos
Hi Robert,

 

I have followed your blog and the build was successful, but the plugin is not connected. What could be the problem ?

 

Regards,

Timothy
R_Zieschang
Contributor
Hi nsetab ,

which CCO Version are you running? I assume you are above > 2.0 FP06?

The plugin was built for 2.0 FP06.

See pom.xml
	<properties>
<sap.scco.pluginClass>com.be1eye.cco.blogpluginpart1.App</sap.scco.pluginClass>
<sap.scco.POSVersions>n/a, 2.0 FP06</sap.scco.POSVersions>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>

 

You may add your version and built the plugin again.

 

Regards

Robert
nsetab
Explorer
0 Kudos
Hi Robert,

 

Thanks I have changed and the plugin is now connected. My CCO version is 2.0 FP08

 

Regards,

Timothy.
R_Zieschang
Contributor
0 Kudos
Hi nsetab

glad to hear that.

Regards

Robert
ricardo_renteria2
Participant
0 Kudos
Hi rzieschang

could you please explain us how to debug the plugin? In the documentation I see is added a line in run.bat with the port 4000, but when I try to debug with maven in Eclipse, it is running in port 5005. For me is not clear which are the steps to debug the plugin. I'm new using maven.

Regards.
R_Zieschang
Contributor
0 Kudos

Hi ricardo.renteria2

did you check part II of this series? In this part I explained what to configure in eclipse to debug cco plugins. 

 

Regards

Robert

jecrual
Explorer
0 Kudos
I followed all the steps but I got this error, then I compiled it once and then it came out again

Do you helpme please, i also followed the suggestions of the answers but nothing

 

 

 

[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.be1eye.cco:blogpluginpart1:jar:0.0.1-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-shade-plugin is missing. @ line 34, column 13
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] -------------------< com.be1eye.cco:blogpluginpart1 >-------------------
[INFO] Building blogpluginpart1 0.0.1-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ blogpluginpart1 ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory D:\Users\siste\eclipse-workspace\blogpluginpart1\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ blogpluginpart1 ---
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!
[INFO] Compiling 1 source file to D:\Users\siste\eclipse-workspace\blogpluginpart1\target\classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[3,30] package com.sap.scco.ap.plugin does not exist
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[9,26] cannot find symbol
symbol: class BasePlugin
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[12,9] method does not override or implement a method from a supertype
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[18,9] method does not override or implement a method from a supertype
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[24,9] method does not override or implement a method from a supertype
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[27,24] cannot find symbol
symbol: method getClass()
location: class com.be1eye.cco.blogpluginpart1.App
[INFO] 6 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.788 s
[INFO] Finished at: 2021-01-28T16:30:43-06:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project blogpluginpart1: Compilation failure: Compilation failure:
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[3,30] package com.sap.scco.ap.plugin does not exist
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[9,26] cannot find symbol
[ERROR] symbol: class BasePlugin
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[12,9] method does not override or implement a method from a supertype
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[18,9] method does not override or implement a method from a supertype
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[24,9] method does not override or implement a method from a supertype
[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[27,24] cannot find symbol
[ERROR] symbol: method getClass()
[ERROR] location: class com.be1eye.cco.blogpluginpart1.App
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
R_Zieschang
Contributor
0 Kudos
Dear jecrual,

 

it seems, that the ENV.jar from CCO is not correctly added in your eclipse project. This is indicated by the error log:

[ERROR] /D:/Users/siste/eclipse-workspace/blogpluginpart1/src/main/java/com/be1eye/cco/blogpluginpart1/App.java:[3,30] package com.sap.scco.ap.plugin does not exist

 

Can you please double check, if the ENV.jar is in your build path?

 

Regards

Robert
jecrual
Explorer
0 Kudos
I added from C:\SapCustomerCheckout\env.jar

This is example blogpluginpart1 compile correct if i create with a project eclipse is correct or only is correct create plugin with MAVEN project?

 

Thanks Robert!!

gombo
Explorer
0 Kudos
Hello, Robert

I'm working on a project where multiple CCO software connected to single Business One server.

New customers can be created on any of these CCO or Business One clients.

Standard CCO function is synchronizing all customers which is unnecessary from my point of view.

Because some customers will often use specific CCO.

I would like to develop plugin where it's possible to sync only specific customers on CCO.

So far I able to call Business One service to select customer data.

But I don't know the specific class & method which will save/create/sync customer  in CCO.

Calling this class & method, I like to pass the selected customer from the service which will work like standard CCO function.

Any kind of help will be really appreciated.

 
siddayya
Member
0 Kudos
In the CCO project I found


"PluginConfigurationType,




PluginConfigurationDTO"




classes need for plugin configuration based on the reference documentation. In the


com.sap:scco:* package there is no classes that I mentioned.


But in the reference they have used those classes.

Kindly give answer.

above.




ramzychehab
Explorer
0 Kudos

Dear Mr. Robert,

I am trying the implement the following for CCO 2.0. 
I have read the post you've made concerning the changes, but that didn't help with the steps provided on this blog. For instance, when creating a new Maven project, Eclipse asks for what type of archetype I would like to use. I picked maven-archetype-quickstart. Concerning the run.bat file, the lines you have highlighted aren't there on my file. 
As for the rest of the steps I was able to follow everything line by line, but when I connect to CCO the plug-in section displays as empty.

Any help would be appreciated,

Labels in this area