This blog promotes knowledge sharing through experience and collaboration. For more product information, visit our WebSphere Commerce CSE page. For easier navigation, utilize the Categories to find posts that match your interest.
V9 Chats: Customization
In this V9 Chats series, we go to the source and interview Commerce experts from the Development, Services and Support teams, who share their insight into the new features and capabilities of WebSphere Commerce V9.
Q: Let me start by asking about the new customization model?
Q: Will all the customizations need to run in the Xc server? What if I have a lot of customization in the transaction server, do I have to migrate those?
Also, IBM Services would be able to help migrate existing customization to the new Xc Model.
Zhen: It is not necessary to move your existing customizations. You have the option to move it, but that would need to be analyzed case by case. Generally speaking, the new xC model is more suitable for lightweight integration scenarios; a typical example is an integration with 3rd-party payment and tax systems.
Q: For new development, is it better to utilize the Xc model or continue to use traditional method? What's the benefit to using Xc model?
Q: If I can't find the Xc extension I need, is it OK to use the traditional model?
Q: What is the customization Server? Would I be able to create my own server and maybe implement with node js?
Zhen: We create a new customization server to deploy new Xc code, so it runs separately from the transaction/search server. The customization server is now based on liberty, so it can NOT support node.js, but since Xc model is based on http rest api, but the interaction with different backend technology stacks is a roadmap in the future.
Q: Was there an upgrade to the product stack?
Q: Looks like V9 runs in docker, does the Toolkit also run in docker?
Jeff: No, the toolkit does not support docket at this point.
So, if we get a new updated docker container for runtime, how would that impact my traditional customizations?
Zhen: This is a big topic. But basically, you need to build up your owner customization docker container with all your customization on top of our OOTB docker container, and run the customized container.
Q: Now, how is the customization model going to impact data access? Is there any change in the use of EJB, etc...
with session bean 3.0, which are very different. As for the client code to use EJB, it also changes. Although we still wrap the JPA in access bean, some method signatures are changed/removed. And the way to
Q: What is the benefit of using JPA?
Q: Can I still create and use custom tables? Is this available from Xc customization model?