tekstream.com

Login to the appropriate Identity Management tool Create a new group and assign users to that group Name the new group Assign users to the new group Click “Create” to create the new group with selected users Repeat for any additional groups that are required Create the new Security Accounts in WebCenter Content: Login to WebCenter Content as an administrator 5. Add the new entries for the new folder Add the new folder with security attributes in Content UI for WebCenter Content: Login to WebCenter Content UI as an administrator In the Folder Properties dialog box switch to the Security tab and ensure that the new account is selected and then click Save At this point, you should be able to login with the users that you assigned to the new group in IdM and verify that they see the appropriate new folder. * Alternatively, only do some test content and only contribute ‘real’ content when PROD is ready Want to learn more about custom document security in Oracle WebCenter Portal 12c?

Well, today I try to take one of those worries off your chest by walking you through a Splunk KvStore Migration, more specifically migrating the Splunk KvStore from a Search Head Cluster to a new Search Head Cluster. The KvStore captain is the instance in the search head cluster that receives the write operations regarding the KvStore collections where the Search head captain is the instance in the search head cluster that schedules jobs, pushes knowledge bundles to search peers, and replicates any runtime changes to knowledge objects throughout the search head cluster.**note Go on each new search head cluster member (CLI) and edit server.conf to have: Also, on each instance, you have to edit/change the search head replication factor to 1 in the new environment on each search head cluster member. Once you have the kvstore captain = search head captain, Log into the CLI of the other search head nodes (every search head cluster member that is not the captain/kvstore captain).

Over the years, I have found one tried and true method for getting Splunk connected to multiple Microsoft SQL Server instances spread across a corporate network—connect to Windows from Windows. —a service account for Splunk to use to connect to all the SQL Server instances and a server running Microsoft Windows. After you have Splunk running under the MSSQL service account with DB Connect installed as an app in the Splunk instance, you’ll want to install the Java Runtime Environment (JRE) software, either version 8 (https://www.oracle.com/java/technologies/javase-jre8-downloads.html) or version 11 (https://www.oracle.com/java/technologies/javase-jdk11-downloads.html), and download the appropriate MSSQL driver based on Splunk’s documentation (https://docs.splunk.com/Documentation/DBX/latest/DeployDBX/Installdatabasedrivers), which either the Microsoft drivers for the open source jTDS drivers. So, after setting up the connection information where the host is the listener and the port is the listener port, click the “Edit JDBC URL” checkbox and add “;instance=<database instance name>” to the end of the JDBC URL to ensure you connect to the proper database instance in the cluster.

Creating Alerts via the Spunk REST API is fairly straightforward once you know exactly what parameters to use to ensure that Splunk recognizes the Saved Search as an Alert. (if this is set to ‘always’, which is the default, Splunk thinks it’s just a report) true (this is a Boolean setting that Splunk checks to make sure there’s a set schedule for the report, which is required for alerts) You’ll use the previous endpoint you used to manage a specific saved search, but you’ll add a new section at the end for “acl” (i.e. ‘https://localhost:8089/services/saved/searches/ATestRESTSearch/acl’). Once the REST call is made, navigate to your “Searches, Reports, and Alerts” screen in Splunk Web, and click to Edit Permissions of your alert.