Category: WebSphere Commerce v8
-
Adding/Changing JVM Parameters with WebSphere Commerce
A lot of parameters that can be set by JVM arguments are available in the WebSphere Admin Console, but sometimes, you just want to set parameters with JVM arguments. You have two options. First, you can use the admin console to set the parameters, and second, you could just update the server.xml file directly. Changing…
-
B2B Contracts: Price Rules and Catalog Filters
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…
-
Basic Authentication Header When Using Webservices Over HTTP
When working with a web service that was failing, tcpmon showed an error page being returned. The page was an HTML 401 Unauthorized error. Despite the web service having a username and password set, and set correctly, the error continued to happened. <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>The_Right_User</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">The_Right_Password</wsse:Password> </wsse:UsernameToken> </wsse:Security> The reason for the error…
-
Debugging SOAP Requests with Logging and TCP/IP Monitor
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…
-
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…
-
Fixing the SolrServerException: IOException Occurred When Talking to Sever
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…
-
Imported EJB Project Isn’t Acting as an 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…
-
Specifying the SSL Version to Fix ‘Received Fatal Alert: Protocol_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…
-
SSL_ERROR_NO_CYPHER_OVERLAP
If you published a new store and go to https://localhost/webapp/wcs/stores/servlet/en/newstore, you just might end up with the Firefox error: SSL_ERROR_NO_CYPHER_OVERLAP To get around that error, type about:config into the Firefox address bar. Using the search box, enter in security.tls_.version.max Double click on the preference name and change the value to 1 After that, you should…
-
Adding a New Finder to an Existing Access Bean
In the WebSphereCommerceServerExtensionsData project using the Java EE perspective, double click the deployment descriptor. Click on the Details button next to the Enterprise Java Bean section or go directly to the bean tab. Select your bean from the list of beans on the left. Then, on the right, scroll down to finders and select Add.…