1.
An implementation professional runs a test of a web service in an IBM Sterling Order Management solution deployed in IBM WebSphere Application Server. The web service crashes with no error details nor relevant information in the log files. The implement needs to re-run the test modifying the log level to obtain more details and fix this issue. How can the log level be modified without restarting the application?
2.
Which option is NOT an advantage of using the indexing solution in an IBM Sterling Order Management V9.4 implementation?
3.
In the following scenario, the system should avoid locking in YFS_INVENTORY_ITEM until the overall availability is low (150). How can this requirement be modeled in the system?
4.
Sales orders are being purged using the ORDER_PURGE transaction for which the retention days period is defined to be 30 days. How does the purge agent select the orders that need to be purged?
5.
An implementation professional installs IBM Sterling Order Management in Upgrade mode. Which attribute needs to be reset in the sandbox.cfg properties file?
6.
An implementation professional needs to implement the use of Promising server and database sharding. Which version(s) of IBM Sterling Order Management needs to be installed?
7.
During a Silent installation of the application, if a user does NOT want to perform any of the database operations, which setting needs to be configured?
8.
Application server data source connection pooling needs to be enabled for an IBM Sterling Order Management V9.4 application deployed on Oracle WebLogic Application Server 12c and Oracle Database 11g (11.2.0.4). Which configuration will enable data source connection pooling?
9.
On any given Order List screen, pagination needs to be implemented. What can the implementation professional do to accomplish this? In the Application Manager, go to Application Platform > Presentation > Resources > Sterling Supply Chain Application Console (YFSSYS00004), then:
10.
A custom API needs to be developed to evaluate the price of a given order. Different kinds of pricing model types, such as "REGULAR", "PROMOTION", "HOLIDAY" and "SEASONAL" are used. The implementation professional wants to set this up so that the custom API code does not have to invoke an API to retrieve the pricing model type. How can this be achieved if the pricing model type that needs to be used by the custom API should be set up as a configurable parameter?