B2B Contracts: Price Rules and Catalog Filters

b2b contracts

Contract Overview Contracts allow an organization or customer group to purchase specific products from a store and a specific price for a specific time. They allow catalog filtering and price rules to be applied to products that change the items available for purchase along with the price of those items. This contract can then be assigned to a customer group or organization in the B2B model. Creating a Price Rule Log into Management Center and select the Catalog Filter and Pricing option. You can make any kind of price rule you need for the contract. A simple example is to […]

Specifying the SSL Version to Fix ‘Received Fatal Alert: Protocol_Version’

wcs ssl version

Changing the SSL version that is used for making outbound requests is becoming more common as versions are being deprecated. If using one of the older versions, you will get the Received Fatal Alert: Protocol_Version error. Changing the version with JVM parameters is possible, but the easy way to change it is through the WAS administration console. SSL certificate and key management > SSL configurations > NodeDefaultSSLSettings > Quality of protection (QoP) settings Select TLSv1.1 for the Protocol.

Imported EJB Project Isn’t Acting as an EJB Project

rad import ejb project

Continuing troubleshooting a payment plugin, the plugin configuration was found, but then a new error was being thrown: Error:Failed to initialize the payment plug-in ThePluginName. The reported exception is: javax.naming.NameNotFoundException: Context: localhost/nodes/localhost/servers/server1, name: ejb/com/company/payment/plugin/ThePluginNameHome: First component in name payment/plugin/ThePluginNameHome not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]. The payment plugin project was there. It was imported and could be found at the path specified. A quick prepare for deployment and publish should fix the issue. However, the imported project into Rational Application Developer was not being treated as an EJB project. Therefore, prepare for deployment wasn’t an option. RAD, as well […]

Failed to get the Plug-in Implementation


Failed to get the plug-in implementation, check the plug-in configuration for payment system name ThePluginName and payment configuration ID default. This FoundationApplicationException will be thrown when you add a new payment plugin in, but have an issue with the PluginDeployment.xml file. First, check you have a folder for the plugin: WC/xml/config/payments/ppc/plugins/ThePluginNamePlugin Second, verify there is a PluginDeployment.xml file located in that folder. Third, the most likely issue, verify the PluginInformation line. The jndi and home attributes need to be set according to your payment plugin. If you have the source, you can verify the correct values in the ibm-ejb-jar-bnd.xml file […]

Debugging SOAP Requests with Logging and TCP/IP Monitor

set up tcpmon for wcs

While working on a project, a SOAP request kept failing. The page wouldn’t load, and I was getting the following lines in the logs: J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source. This is the multithreaded access detection option. Alternatively check that the Database or MessageProvider is available. J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource eis/JCAHTTP-WS. The exception is: java.io.IOException: javax.xml.soap.SOAPException: org.xml.sax.SAXParseException: White space is required between “SYSTEM” and the system identifier. Message being parsed: Trace Strings […]

Fixing the SolrServerException: IOException Occurred When Talking to Sever

di-buildindex ioexception occured while talking to solr server

From a recent post, you may need to restore your local RAD DB2 database, and it may or may not be a backup from another toolkit. When the database is restored, all the data you need is there, but Solr is still not returning the expected products. So you open a command prompt, and cd into┬ác:\IBM\WCDE80\bin. Run the preprocessor for your master catalog or your catalog asset store, which we will pretend is 12345: Everything works fine, and then you go to di-buildindex since that’s mainly what you wanted: And you end up with a terrible stack trace like so: […]