Search for existing answers to your product and support questions.
Familiarize yourself with our support site and learn best practices in working with our team.
Manage Service Requests, View and update service requests submitted by you and others in your organization.
Submit a new issue to our technical support team.
Oracle B2C Service insights from our Technical Support team subject matter experts
Browse resources to assist you in launching your implementation and ensure a successful go-live.
Access your OCI account.
Find product documentation for supported versions of B2C and documentation libraries for related service solutions.
You will have the tools to improve your customers' experience when you learn about all the things our products can do.
Find links for API documentation, Custom Processes, Customer Portal, and Agent Browser UI Extensibility Framework.
Explore how accelerators are designed to demonstrate how an integration scenario could be built using the public integration and extension capabilities of the Oracle B2C Service.
Prepare for a successful transition by reviewing upcoming release changes and enhancements.
Explore webinars, events, and feature kits to learn about B2C Service features, functionality, and best practices from the technical experts.
Oracle MyLearn offers a portfolio of free and paid subscription-based learning resources to help you gain valuable skills, accelerate cloud adoption, increase productivity, and transform your business.
Empower your team with the skills to implement, configure, manage, and use your applications with Customer Experience Cloud Training.
Our goal is to facilitate a friendly, supportive environment where members can easily collaborate with each other on solutions and best practices.
Ask and answer questions specific to B2C.
This is an exciting resource intended to help with your Oracle Service Cloud Analytics.
Share product improvement ideas and enhancement requests with Oracle Development, while collaborating with other Oracle customers and partners.
Update your phone number, email notification preferences, and severity 1 and severity 2 contact preferences.
View the contact managers within your organization.
Find contact information of the Technical Account Manager (TAM) and Client Success Manager (CSM) for your organization.
Environment:
Knowledge Advanced Oracle B2C Service 19B release and later
Resolution:
Knowledge Advanced (KA) content processing jobs are found at the bottom of the Collection Setup. These jobs crawl and index KB content, web content, and external content to make it available in the Search on the agent desktop, Browser UI and CP web portal. There are several different jobs in the content processing.
Please see the Documentation for a full description of each type of job in the Content Processing Documentation.
The incremental crawl job is two jobs, crawling and indexing. For incremental changes in content to become visible to the users during search an indexing job has to process the content after its crawl job completes. The incremental jobs are optimized to run every 15 minutes in parallel, this allows for more frequent updates to the KB articles. Generally this means that an article update will be available in search between 15 to 30 minutes after the change.
The Full content processing jobs are also scheduled or can be run on demand.
The Queue button can be used to add additional processing for each type of job. This is used for the on demand type jobs and can be used to run additional once a day or once a week jobs as they are needed. It is not helpful to queue the incremental jobs as they are already running every 15 minutes. The incremental jobs are started by a utility that runs every 15 minutes so queuing them will not run them more quickly.
If a full crawl is queued it will take the place of the next incremental crawl. It is good to run full crawls after authoring has slowed down for the day and the incremental crawls are not needed.
When a job is already queued you do not need to queue another job of the same type.
The web crawl only runs 1 time a week unless it is run manually from the collection setup page. The utility still runs every 15 mintues to check if a manual update has been queued. The reasons that it is only scheduled to run once a week is because it is not an incremental crawl. There are no reliable way to determine if a webpage has been updated/changed. So the Web crawl is always a full crawl. Also the website can be a large amount of crawling. Depending on how it is set up in the collection definition, recursively with N-level depth. And websites tend to be more 'static' in nature.