was it working inside the DEVELOPER?
Is there any JDBC connect to any external data?
It worked perfectly inside developer.
No JDBC connection.
Simple reading field and output data.
Input --> <Item number>
rest APi - /Article/byIdentifiers?identifiers=<Item number>&fields=ArticleLang.DescriptionShort(EN)
Output Expected - <Description String>
Works in developer as standalone calling restclient with url, id and passwd
I am using InternalrestClient when deploying to PIM
Class clazz = Class.forName( "com.heiler.ppm.webservice.server.internal.InternalRestClient" );
First highlighted error,
//RestClient restClient = new RestClient();
//restClient.loginWithBasicAuth(basicUrl, userName, password, Locale.ENGLISH);
RestClient restClient = getRestClient();
Second highlighted error log
RestClient restClient = new RestClient();
restClient.loginWithBasicAuth(basicUrl, userName, password, Locale.ENGLISH);
//RestClient restClient = getRestClient();
Any way out for this please?
I struggled through previous errors and stuck here at the moment
I´m sorry but I´m no IDQ developer. If the REST Call is working in for Example POSTMAN it should also work inside the rule.
Hint: You can compare some already working rules with yours because I´ve seen issue where the body of the authentication was different which looks very similar to that issue here.
So please compare your authentication with a already working default rule.
Yeah I was also thinking the internal REST client doesn't even need an authentication at all. Not sure if that helps though either.
Thank you Stefan for the update.
So I have checked with both
1. Passing with user name, password for authentication (no internalrestclient)
2. As suggested with Documentation, using Internal rest client.
Both of these result in the same as updated above.
[LDTM_0072] No errors encountered.]
Did you check your authentication mode with a default rule?
The default rules do not have rest api calling.
However, I installed a simple function rule calling
1. simple function to concatinate
2. java function to substring.
some of the complex rules do like check PresetValues and so on they should contain Java Code with REST because they need information from PIM.
But as long as it is working now its perfect.
My bad Ralph,
I just checked the 'Check_Presetvalues' and it is internally using InternalRestClient.
However cross verifying the code looks almost similar.
I will get this checked as well.
Thank you for the inputs ,
Cross verified with the code and execution.
It works fine with Check_Preset.
Guess, I need to Look through the code now further.