Log.properties for OIM

Hi all,
can anybody explain the following parameters in log.properties
log4j.appender.logfile.MaxFileSize=1000MB
log4j.appender.logfile.MaxBackupIndex=20
I am assuming the first is the max size of log file. Then the file will truncated and create a new one. but is there a way to archive the file before that, may be 10 files?
Is there a way to delete the log file daily/weekly instead of size.
I have no idea about the second. what does that do?
Can I find any document or something where i can find what each parameter is for?
Your help is appreciated.
Thanks

Log4j documentation will answer all your questions: http://logging.apache.org/log4j/1.2/manual.html
Hope this helps
/Martin

Similar Messages

Logging.properties change for Applets

I'm trying to change the property java.util.logging.FileHandler.formatter in the logging.properties file. I've specified the name of the class which extends Formatter, and changed the CLASSPATH environment variable to locate the class.
However, the default XMLFormatter is still being used.
I've also had problems setting Preferences and LoggingPermission permissions in the policy file. Does anyone have any success with getting this to work?
Thanks in advance for any help you may be able to provide.

John L. wrote:
I'm trying to change the property java.util.logging.FileHandler.formatter in the logging.properties file. I've specified the name of the class which extends Formatter, and changed the CLASSPATH environment variable to locate the class.
Applets in a browser run in a sandbox. And I am rather certain that the OS env classpath variable has no impact on that. I could be wrong though.
You might want to research how applets work in general from that you might be able to determine the best way to approach your problem.

Log.properties

below is the log.properties file but this is not able to generate new log file every hour.
so please help me to point out what modification should be needed.
# This file is to configure the logs that xellerate produces via log4j.
# this file is used by Websphere and Weblogic. If JBoss is used
# to host Xellerate, the file that needs to be modified is jboss-log4j.xml under
# the JBoss directory: <jboss_home>/server/default/conf. Since
# this file is used for the whole JBoss log configuration, a Xellerate
# tag is used to define the level to log:
# <category name="XELLERATE">
# <priority value="WARN"/>
# </category>
# That is equivalent to the line below:
# log4j.logger.XELLERATE=WARN
# If specific categories need to be logged as in the case of the commented
# categories below, a new category can be added after the "XELLERATE" category
# in the jboss-log4j.xml file for JBoss. For instance "XELLERATE.ACCOUNTMANAGEMENT"
# as below, would be like the following in jboss-log4j.xml:
# <category name="XELLERATE.ACCOUNTMANAGEMENT">
# <priority value="DEBUG"/>
# </category>
# In the case of Weblogic or Weblogic, uncommenting the category below would
# be enough.
# Any changes to the log configuration need to be follow by a restart of the
# Application Server.
# For more information about log4j, please refer to http://logging.apache.org/log4j/docs/
# The below configuration sets the output of the log to be to the
# standard output. In the case of JBoss it is to the console and
# for Websphere and Weblogic to the log file.
# Commentted below is "logfile" in addition to stdout. If you want
# the output to be sent to a specific file un-comment the line below
# and comment the one without the "logfile" entry.
log4j.rootLogger=WARN,stdout,logfile
#log4j.rootLogger=WARN,stdout
# Console Appender
# The configuration below is to configure the way the log will be formatted
# when it is output to the console.
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%5p,%d{dd MMM yyyy HH:mm:ss,SSS},[%c],%m%n
# File Appender
# Uncomment if you want to output to a file and change the file name and path
log4j.appender.logfile=org.apache.log4j.DailyRollingFileAppender
log4j.appender.logfile.DatePattern='.'yyyy-MM-dd-HH
log4j.appender.logfile.File=F:/OIM/oimserver/logs/OIMLOG.log
log4j.appender.logfile.MaxBackupIndex=20
log4j.appender.logfile.layout=org.apache.log4j.PatternLayout
log4j.appender.logfile.layout.ConversionPattern=%p %t %c - %m%n
# Below are the different categories supported by Xellerate
# commented out. The Root Category, .XELLERATE, is not commented
# out and it's set to WARN. This means that every category is set
# to WARN level unless specifically changed. Each category can be
# uncommented and the level can be changed individually while
# the root is still on WARN (for all other categories with log level
# not defined).
# The following are the accepted levels:
# DEBUG - The DEBUG Level designates fine-grained informational events
# that are most useful to debug an application.
# INFO - The INFO level designates informational messages that highlight
# the progress of the application at coarse-grained level.
# WARN - The WARN level designates potentially harmful situations.
# ERROR - The ERROR level designates error events that might still allow
# the application to continue running.
# FATAL - The FATAL level designates very severe error events that will
# presumably lead the application to abort.
# Special Levels:
# ALL - The ALL Level has the lowest possible rank and is intended to turn on all logging.
# OFF - The OFF Level has the highest possible rank and is intended to turn off logging.
# XELLERATE #
log4j.logger.XELLERATE=WARN
# We would like to have DDM operations at the DEBUG level
# as we may not have a second chance to perform the same
# operation if something fails
log4j.logger.XELLERATE.DDM=DEBUG
#log4j.logger.XELLERATE.ACCOUNTMANAGEMENT=DEBUG
#log4j.logger.XELLERATE.SERVER=DEBUG
#log4j.logger.XELLERATE.RESOURCEMANAGEMENT=DEBUG
#log4j.logger.XELLERATE.REQUESTS=DEBUG
#log4j.logger.XELLERATE.WORKFLOW=DEBUG
#log4j.logger.XELLERATE.WEBAPP=DEBUG
#log4j.logger.XELLERATE.SCHEDULER=DEBUG
#log4j.logger.XELLERATE.SCHEDULER.Task=DEBUG
#log4j.logger.XELLERATE.ADAPTERS=DEBUG
#log4j.logger.XELLERATE.JAVACLIENT=DEBUG
#log4j.logger.XELLERATE.POLICIES=DEBUG
#log4j.logger.XELLERATE.RULES=DEBUG
#log4j.logger.XELLERATE.DATABASE=DEBUG
#log4j.logger.XELLERATE.APIS=DEBUG
#log4j.logger.XELLERATE.OBJECTMANAGEMENT=DEBUG
#log4j.logger.XELLERATE.JMS=DEBUG
#log4j.logger.XELLERATE.REMOTEMANAGER=DEBUG
#log4j.logger.XELLERATE.CACHEMANAGEMENT=DEBUG
#log4j.logger.XELLERATE.ATTESTATION=DEBUG
#log4j.logger.XELLERATE.AUDITOR=DEBUG
#log4j.logger.XELLERATE.PERFORMANCE=DEBUG
# SPML Webservice #
log4j.logger.SPMLWS=WARN
log4j.logger.SPMLWS.OIMEvent=DEBUG
# Nexaweb #
log4j.logger.com.nexaweb.server=WARN
# OSCache #
log4j.logger.com.opensymphony.oscache=ERROR

Why are you expecting to generate a new log file every hour ? It will keep updating the same log file and archive it ...
Thanks
Suren

Testing Oracle Internet Directory Connector for OIM

Hello,
I'm trying to test the running test cases available in the Oracle Internet Directory Connector for OIM but I'm failing because it seems that the current release of this connector doesn't have the java class tcUtilTestOID as described in the documentation. This class should be at test\troubleshoot\scripts directory, but there there are only the batch files with the test cases.
Can anyone confirm this or provide me this class file?
Thanks in advance.

This is the code. Include this in your custom jar file with the same name. You will be done I suppose:
import com.thortech.util.logging.Logger;
import com.thortech.xl.integration.OID.util.tcUtilLDAPOperations;
import java.io.*;
import java.util.Properties;
import javax.naming.directory.BasicAttribute;
import javax.naming.directory.BasicAttributes;
public class tcUtilTestOID
private static String CONFIG_FILEPATH = "global.properties";
public tcUtilTestOID()
public static void main(String args[])
tcUtilLDAPOperations ldapOp = null;
Logger logger = Logger.getLogger("TEST_USER_PROVISION");
logger.info("**********************************");
logger.info("**********************************" + args[0]);
try
FileInputStream configfile = null;
try
configfile = new FileInputStream(CONFIG_FILEPATH);
catch(FileNotFoundException fe)
logger.error("Unable to find configfile(" + CONFIG_FILEPATH + ")");
fe.printStackTrace();
Properties prp = new Properties();
try
prp.load(configfile);
catch(IOException ie)
logger.error("Unable to load configfile(" + CONFIG_FILEPATH + ")");
ie.printStackTrace();
String serverName = prp.getProperty("serverName");
String portNo = prp.getProperty("portNo");
String rootContext = prp.getProperty("rootContext");
String principalDN = prp.getProperty("principalDN");
String principalPass = prp.getProperty("principalPassword");
boolean sslFlag = "true".equalsIgnoreCase(prp.getProperty("sslFlag"));
logger.info("serverName = " + serverName);
logger.info("portNo = " + portNo);
logger.info("rootContext = " + rootContext);
logger.info("principalDN = " + principalDN);
logger.info("sslFlag = " + sslFlag);
logger.info("===================================\n");
ldapOp = new tcUtilLDAPOperations(serverName, portNo, rootContext, principalDN, principalPass, sslFlag);
String ldapUserDNPrefix = "cn";
String ldapObjectClass = "objectclass";
String ldapUserObjectClass = "inetOrgPerson";
String ldapFirstName = "givenName";
String ldapLastName = "sn";
String ldapCommonName = "cn";
String ldapPassword = "userPassword";
String containerDN = prp.getProperty("containerDN");
logger.info("containerDN = " + containerDN);
logger.info("UserOperation selected = " + args[0]);
if(args[0].equalsIgnoreCase("createUser"))
logger.info(" CREATE USER CALLED");
String createUserFName = prp.getProperty("createUser.firstName");
String createUserLName = prp.getProperty("createUser.lastName");
String createUserUserDN = prp.getProperty("createUser.userDN");
String createUserUserPass = prp.getProperty("createUser.userPassword");
logger.info("createUser.firstName = " + createUserFName);
logger.info("createUser.lastName = " + createUserLName);
logger.info("createUser.userDN = " + createUserUserDN);
logger.info("createUser.userPassword = " + createUserUserPass + "\n\n");
BasicAttributes basicattributes = new BasicAttributes(true);
basicattributes.put(new BasicAttribute(ldapObjectClass, ldapUserObjectClass));
basicattributes.put(new BasicAttribute(ldapFirstName, createUserFName));
basicattributes.put(new BasicAttribute(ldapLastName, createUserLName));
basicattributes.put(new BasicAttribute(ldapCommonName, createUserFName + " " + createUserLName));
basicattributes.put(new BasicAttribute(ldapPassword, createUserUserPass));
ldapOp.connectToLDAP();
boolean userCreated = ldapOp.createObject(ldapUserDNPrefix + "=" + createUserUserDN + "," + containerDN, basicattributes);
ldapOp.disconnectFromLDAP();
if(userCreated)
logger.info("\t>> " + createUserUserDN + " - USER_CREATION_SUCCESSFUL");
} else
logger.info("\t>> " + createUserUserDN + " - USER_CREATION_FAILED");
} else
if(args[0].equals("modifyUser"))
logger.info(" MODIFY USER CALLED");
String modifyUserUserDN = prp.getProperty("modifyUser.userDN");
String modifyUserParamName = prp.getProperty("modifyUser.paramName");
String modifyUserParamValue = prp.getProperty("modifyUser.paramValue");
logger.info("modifyUser.userDN = " + modifyUserUserDN);
logger.info("modifyUser.paramName = " + modifyUserParamName);
logger.info("modifyUser.paramValue = " + modifyUserParamValue);
ldapOp.connectToLDAP();
BasicAttributes basicattributes = new BasicAttributes(true);
basicattributes.put(new BasicAttribute(modifyUserParamName, modifyUserParamValue));
boolean isUserModified = ldapOp.modifyAttributesReplace(ldapUserDNPrefix + "=" + modifyUserUserDN + "," + containerDN, basicattributes);
ldapOp.disconnectFromLDAP();
if(isUserModified)
logger.info("\t>> " + modifyUserUserDN + " - USER_UPDATE_SUCCESSFUL");
} else
logger.info("\t>> " + modifyUserUserDN + " - USER_UPDATE_FAILED");
} else
if(args[0].equals("deleteUser"))
logger.info(" DELETE USER CALLED");
String deleteUserUserDN = prp.getProperty("deleteUser.userDN");
logger.info("deleteUser.userDN = " + deleteUserUserDN);
ldapOp.connectToLDAP();
boolean isUserDeleted = ldapOp.deleteObject(ldapUserDNPrefix + "=" + deleteUserUserDN + "," + containerDN);
ldapOp.disconnectFromLDAP();
if(isUserDeleted)
logger.info("\t>> " + deleteUserUserDN + " - USER_DELETION_SUCCESSFUL");
} else
logger.info("\t>> " + deleteUserUserDN + " - USER_DELETION_FAILED");
catch(Exception e1)
e1.printStackTrace();
return;
Thanks
Sunny

Configure clustering for OIM

Hi Experts,
We have not configured clustering for OIM during installation. Just wanted to check on whether it is possible to configure clustering and add servers to the cluster post installation. If yes could you please share a link or document which tells us how to achieve this.
Thanks

Thanks for the reply but even after making the modification I am getting the same error as earlier.
tcSignatureMessage moSignature = tcCryptoUtil.sign("xelsysadm","PrivateKey");
The above line is throwing error. It is unable to create the object it seems.
The current code looks like this
System.setProperty("XL.HomeDir", "E:/oracle/xlclient");
System.setProperty("java.security.policy","E:/oracle/xlclient/Config/xl.policy");
System.setProperty("log4j.configuration","E:/oracle/xlclient/Config/log.properties");
// Get connection to OIM Server
ConfigurationClient.ComplexSetting config = ConfigurationClient.getComplexSettingByPath("Discovery.CoreServer");
Hashtable env = config.getAllSettings();
tcSignatureMessage moSignature = tcCryptoUtil.sign("xelsysadm","PrivateKey");
factory = new tcUtilityFactory(env, moSignature);
userOper = (tcUserOperationsIntf) factory.getUtility("Thor.API.Operations.tcUserOperationsIntf");
And the error message remains the same as in the earlier post.
@Rajiv: I dont have access to MetaLink. But thanks for the reply.

(Cisco Historical Reporting / HRC ) All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054

Hi All,
I am getting an error message "All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054" when trying to log into HRC (This user has the reporting capabilities) . I checked the log files this is what i found out
The log file stated that there were ongoing connections of HRC with the CCX (I am sure there isn't any active login to HRC)
|| When you tried to login the following error was being displayed because the maximum number of connections were reached for the server . We can see that a total number of 5 connections have been configured . ||
1: 6/20/2014 9:13:49 AM %CHC-LOG_SUBFAC-3-UNK:Current number of connections (5) from historical Clients/Scheduler to 'CRA_DATABASE' database exceeded the maximum number of possible connections (5).Check with your administrator about changing this limit on server (wfengine.properties), however this might impact server performance.
|| Below we can see all 5 connections being used up . ||
2: 6/20/2014 9:13:49 AM %CHC-LOG_SUBFAC-3-UNK:[DB Connections From Clients (count=5)]|[(#1) 'username'='uccxhrc','hostname'='3SK5FS1.ucsfmedicalcenter.org']|[(#2) 'username'='uccxhrc','hostname'='PFS-HHXDGX1.ucsfmedicalcenter.org']|[(#3) 'username'='uccxhrc','hostname'='PFS-HHXDGX1.ucsfmedicalcenter.org']|[(#4) 'username'='uccxhrc','hostname'='PFS-HHXDGX1.ucsfmedicalcenter.org']|[(#5) 'username'='uccxhrc','hostname'='47BMMM1.ucsfmedicalcenter.org']
|| Once the maximum number of connection was reached it threw an error . ||
3: 6/20/2014 9:13:49 AM %CHC-LOG_SUBFAC-3-UNK:Number of max connection to 'CRA_DATABASE' database was reached! Connection could not be established.
4: 6/20/2014 9:13:49 AM %CHC-LOG_SUBFAC-3-UNK:Database connection to 'CRA_DATABASE' failed due to (All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054.)
Current exact UCCX Version 9.0.2.11001-24
Current CUCM Version 8.6.2.23900-10
Business impact Not Critical
Exact error message All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054
What is the OS version of the PC you are running and is it physical machine or virtual machine that is running the HRC client ..
OS Version Windows 7 Home Premium 64 bit and it’s a physical machine.
. The Max DB Connections for Report Client Sessions is set to 5 for each servers (There are two servers). The no of HR Sessions is set to 10.
I wanted to know if there is a way to find the HRC sessions active now and terminate the one or more or all of that sessions from the server end ?

We have had this "PRX5" problem with Exchange 2013 since the RTM version. We recently applied CU3, and it did not correct the problem. We have seen this problem on every Exchange 2013 we manage. They are all installations where all roles
are installed on the same Windows server, and in our case, they are all Windows virtual machines using Windows 2012 Hyper-V.
We have tried all the "this fixed it for me" solutions regarding DNS, network cards, host file entries and so forth. None of those "solutions" made any difference whatsoever. The occurrence of the temporary error PRX5 seems totally random.
About 2 out of 20 incoming mail test by Microsoft Connectivity Analyzer fail with this PRX5 error.
Most people don't ever notice the issue because remote mail servers retry the connection later. However, telephone voice mail systems that forward voice message files to email, or other such applications such as your scanner, often don't retry and
simply fail. Our phone system actually disables all further attempts to send voice mail to a particular user if the PRX5 error is returned when the email is sent by the phone system.
Is Microsoft totally oblivious to this problem?
PRX5 is a serious issue that needs an Exchange team resolution, or at least an acknowledgement that the problem actually does exist and has negative consequences for proper mail flow.
JSB

Problem while applying BP02 for OIM 11.1.1.5.0

We have OIM-OAM integrated environment enabled with ldapsynch (OID/OVD). We are applying BP02 for OIM 11.1.1.5.0. We followed all the steps provided in the read me doc.
1. Running latest Opatch
2. Setting the environement variables
3. Configuring Weblogic.profile
4. Applying SOA patch 13106312
5. Applied OIM patch 13399365
6. Running patch_weblogic.sh
But while doing the 6th step "Running patch_weblogic.sh" we are facing below exception.
patch:
[echo] unzipping the archives.....
explode-archived-apps:
[delete] Deleting directory /FS2/oracle/apps/MWHOME/Oracle_IDM1/server/apps/oim.ear
[delete] Deleting directory /FS2/oracle/apps/MWHOME/Oracle_IDM1/server/apps/Nexaweb.ear
[mkdir] Created dir: /FS2/oracle/apps/MWHOME/Oracle_IDM1/server/apps/oim.ear
[mkdir] Created dir: /FS2/oracle/apps/MWHOME/Oracle_IDM1/server/apps/Nexaweb.ear
[unzip] Expanding: /FS2/oracle/apps/MWHOME/Oracle_IDM1/server/patching/oim.ear into /FS2/oracle/apps/MWHOME/Oracle_IDM1/server/apps/oim.ear
[unzip] Expanding: /FS2/oracle/apps/MWHOME/Oracle_IDM1/server/patching/Nexaweb.ear into /FS2/oracle/apps/MWHOME/Oracle_IDM1/server/apps/Nexaweb.ear
[echo] archives unzipped successfully.....
[echo]           seeding the out of the box jobs into db
seed-ootb-jobs:
seed-ootb-jobs:
[echo] ----> SEEDING OUT OF THE BOX SCHEDULE JOBS AND TRIGGERS
[java] Feb 9, 2012 1:00:26 PM org.quartz.core.QuartzScheduler <init>
[java] INFO: Quartz Scheduler v.1.6.0 created.
[java] Feb 9, 2012 1:00:27 PM org.quartz.impl.jdbcjobstore.JobStoreSupport initialize
[java] INFO: Using thread monitor-based data access locking (synchronization).
[java] Exception in thread "Main Thread" java.lang.Exception: Unable to seed scheduler data due to configuration problems. Contact System Administrator
[java]      at oracle.iam.scheduler.seed.SeedSchedulerData.startSeeding(SeedSchedulerData.java:770)
[java]      at oracle.iam.scheduler.seed.SeedSchedulerData.main(SeedSchedulerData.java:113)
As it is one of high priority task Can any one help by providing your inputs at earliest ?

Hello All,
Still we haven't able to resolve this issue. We already have SR with oracle. So many logs were captured.
Below is the snippet of seedSchedulerdata.log
${work.dir}Entered Validate methodExiting Validate method------------------------------------------------------------
Start seeding task
job name--> Password Expiration Task
schTaskName--> Password Expiration Task
task class name--> com.thortech.xl.schedule.tasks.tcTskPasswordExpiration
task job disable--> 0
task frequency--> DAILY
task maxRetries--> 5
task retryCount--> 0
task paramName--> Email Definition Name
task paramValue--> Password Expired
task paramTpe--> String
Updating Job :Password Expiration Task with keys
java.lang.Exception: Unable to seed scheduler data due to configuration problems. Contact System Administrator
     at oracle.iam.scheduler.seed.SeedSchedulerData.startSeeding(SeedSchedulerData.java:770)
     at oracle.iam.scheduler.seed.SeedSchedulerData.main(SeedSchedulerData.java:113)
If any of them faced such issue please help.
Thanks
DK

How to change properties for some controls in runtime ?

hi,
I would like to change some of the properties for some controls in front panel in runtime. Number of control properties I want to change is depending of a log file user opens in final application.
I attach an example where I'm trying to change the visibility of numeric controls. Problem I have I don't know which reference to connect to property node in case the control in for loop is not a numeric control. The example relies to label.text property but I could use the more generic classname property as well.
regards,
petri
Solved!
Go to Solution.
Attachments:
dynamic reference.vi ‏11 KB

pcardinale wrote:
Initially, a control has no caption. It's not just that the caption string is empty and the caption not visible, but the caption object does not exist.
I think this should probably be changed in future versions, because even if each control had a caption, it would still be a negligible small part of the VI. The current behavior made sense many years ago where HD and memory space was very precious. Not any more!
This issue comes up often enough that it warrants addressing the root of the problem.
It is hard to convince the casual that the caption does not exist if he can simply do a "show caption" at edit time and it will show in all glory, even with the default set to the current label. It is confusing!
There is even an idea about this that seems worth supporting (also read the link in the discussion).
What do you think?
LabVIEW Champion . Do more with less code and in less time .

Design Console SSL problems for OIM 9.1.0.2

Hi there,
I have installed the design client for OIM 9.1.0.2, patched it and activated SSL using the instructions in:
http://download.oracle.com/docs/cd/E14049_01/doc.9101/e14062.pdf
However, when I attempt to log in, I get the following error at the UI:
Error Keyword: DAE.UNKNOWN_CODE
Description: An unknown error code was passed.
Remedy: Contact your system adminstrator.
Action: E
Severity: C
Help URL:
Detail:
com.thortech.xl.security.tcLoginException: javax.naming.CommunicationException: Server protocol was not ORMI, if uncertain about the port your server uses for ORMI then use the default, 23791 [Root exception is java.io.IOException: Server protocol was not ORMI, if uncertain about the port your server uses for ORMI then use the default, 23791]
This seems to indicate that the server protocol is not ORMI, which is correct, it is ORMIS (as per the SSL instructions).
I've checked through the logs for this error, and am unable to find it, so it looks like it is only visiible client side. This suggests that the connection is not reaching OIM.
Does anyone have any ideas about how to make sure ORMIS is in use and trouble shooting my SSL connection?
Any advice gratefully received,
Hugh

While seting rmis port in opmn.xml file one should ensure that these ports must be unique as per the DC install guide. Please note there are three instances of <port id="rmis" range="1270x"/> in the opmn.xml file. The first one is generic, the second one is for oc4j_home oc4j container and the last for the oim oc4j container. The rmis port for the oim container must be 12701 for the other instructions to work, the others can be 12702 and 12703 so set the first one to 12702, the second one to 12703 and the third one to 12701 respectively.
xlConfig_dc_side I had the following:
<java.naming.provider.url>ormi://172.20.16.139:12701/Xellerate</java.naming.provider.url>
where it should have been:
<java.naming.provider.url>ormis://172.20.16.139:12701/Xellerate</java.naming.provider.url>
This fixed my problem.
2Hugh

Error editing task sequence: Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" From XML into WMI

I've started getting an intermittent error editing my Windows 7 OSD task sequence. Sometimes I can open the TS to edit, but when I try to apply changes I get the error. Other times I get the error when trying to open the TS. If I try again
right away, I still get the error, but if I wait a few minutes and try again sometimes it will open the TS.
The error reads:
ConfigMgr Error Object:instance of SMS_Extended Status{Description = "Failed to load dynamic properties for class \"SMS_TaskSequence_ApplyWindowsSettingsAction\" from XML into WMI";Error Code = 2147943746;File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp";Line = 3454;Operation = "ExecMethod";ParameterInfo = "SMS_TaskSequencePackage";ProviderName = "WinMgmt";StatusCode = 2147749889;}
Coinciding with this error, I show the following entries in the TaskSequenceProvider.log file:
[PID: 7608] Invoking method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Failed to protect memory buffer, hr=0x80070542
TaskSequenceProvider
Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load node Apply Windows Settings from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "PostInstall" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "Execute Task Sequence" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load XML for the task sequence into WMI 0x80070542 (2147943746)
TaskSequenceProvider
[PID: 7608] Done with method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Setting status complete: status code = 0x80070542; Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI
TaskSequenceProvider
I exported the task sequence and checked in "object.xml" for the "ApplyWindowsSettingsAction", to see if there was something odd in the xml, but I don't find anything that jumps out as being wrong. Here's the section of XML for
that step. I've removed identifying info, and replaced it with a generic term in bold.
<step type="SMS_TaskSequence_ApplyWindowsSettingsAction" name="Apply Windows Settings" description="" runIn="WinPE" successCodeList="0" runFromNet="false"><action>osdwinsettings.exe /config</action><defaultVarList><variable name="OSDLocalAdminPassword" property="AdminPassword"></variable><variable name="OSDComputerName" property="ComputerName">%_SMSTSMachineName%</variable><variable name="OSDProductKey" property="ProductKey"></variable><variable name="OSDRandomAdminPassword" property="RandomAdminPassword">false</variable><variable name="OSDRegisteredOrgName" property="RegisteredOrgName">COMPANY NAME</variable><variable name="OSDRegisteredUserName" property="RegisteredUserName">COMPANY NAME</variable><variable name="OSDServerLicenseConnectionLimit" property="ServerLicenseConnectionLimit">5</variable><variable name="OSDTimeZone" property="TimeZone">Central Standard Time</variable></defaultVarList></step><step type="SMS_TaskSequence_ApplyNetworkSettingsAction" name="Apply Network Settings" description="" runIn="WinPEandFullOS" successCodeList="0" runFromNet="false"><action>osdnetsettings.exe configure</action><defaultVarList><variable name="OSDDomainName" property="DomainName">DOMAIN.COM</variable><variable name="OSDJoinPassword" property="DomainPassword"></variable><variable name="OSDJoinAccount" property="DomainUsername">DOMAIN ACCOUNT</variable><variable name="OSDEnableTCPIPFiltering" property="EnableTCPIPFiltering" hidden="true">false</variable><variable name="OSDNetworkJoinType" property="NetworkJoinType">0</variable><variable name="OSDAdapterCount" property="NumAdapters" hidden="true">0</variable></defaultVarList></step>
Is there any other log I should check for a clue on this issue? What could be causing this error?

Thanks for sharing that! I tend to save contacting MS support until after I've exhausted other options. I'm always afraid that I'll spend the $500 to open a case and then it turns out to be something simple that I would have found if I had just
kept working on it myself a little longer.
It looks like that link is for an update released in February as KB3023562. I downloaded and installed it. I'll try opening/editing/saving the task sequence a few times today to see if the issue is resolved.
After I had already installed it, I thought to look up that update in configmgr. The update is listed as superseded by 2 other updates. The newest of those is KB3046049, which just installed last night with the other March patches, so it's possible
that I didn't need to install KB3023562 after all.

**Creating default directory in failed: \logging.properties (Access is denied)**

Hello Experts,
i am deploying edq on weblogic.
After deployment, when lauching the edq url getting below error on firefox.
**Creating default directory in failed: \logging.properties (Access is denied)**
by default, it took the path as:
C:\oraclesw\oracle\middleware\user_projects\domains\oedq_dev_domain\servers\edqdev_server1\tmp\_WL_user\dndirector\1i3bzo\war\WEB-INF\config
i have unzipped the config.zip into above mentioned config folder.

When we restart the application server up and start the managed server, the deployment is in the failed status with the following message:
We have the Memory settings on the managed server set as : -Xmx5024M –XX:MaxPermSize=256M
<Jul 11, 2013 4:45:13 PM EDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating start task for application 'dndirector'.>
<Jul 11, 2013 4:45:13 PM EDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
        at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1520)
        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: com.datanomic.utils.transport.TransportSignature
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        Truncated. see log file for complete stacktrace
>
<Jul 11, 2013 4:49:42 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WebAppApplicationOverviewPage&WebAppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3Ddndirector%2CType%3DAppDeployment%22%29.>

Facing issue when LDAPSync is enabled for OIM-AD integration with SSL enabled

Hi
We are performing LDAPSync for OIM AD real time sync.We have done all configuration as per oracle documentation on LDAPSync for OIM 11gR2 : http://docs.oracle.com/cd/E27559_01/integration.1112/e27123/oid_oim.htm The OIM environment we tested is the latest OIM version OIM 11gR2 PS1 (11.1.2.1.0).
WE have performed LDAPSync enablement on postinstallation of OIM .So we dont have OVD , we have configured libOVD as mentioned in this doc.
We have performed following steps mentioned in this document in our OIM environment.
3.1 Enabling Post installation LDAP Synchronization
3.3 Creating Identity Virtualization Library (libOVD) Adapters and Integrating With Oracle Identity Manager
As attribute like password might be not getting updated in AD from OIM , we have configured SSL enabled integration in LDAP sync as mentioned in above document.
We implemented this step 3.4.1 Enabling SSL Between Identity Virtualization Library (libOVD) and Microsoft Active Directory,
but here it is not properly mentioned that about how to import public key certificate of AD into OIM envirioment for SSL.
We are getting following error message in logs : Looking at logs it looks like the import of AD SSL certificate did not happen properly in OIM environment. But ,we have imported it using keytool and OVD keystore ...please let us know if we are missing any configuration in this process.Above oracle document is not pretty clear on this.
<Dec 7, 2013 12:22:53 AM IST> <Warning> <oracle.ods.virtualization.engine.backend.jndi.LDAP2.BackendJNDI> <OVD-40118> <Could not automatically detect binary attribute list: simple bind failed: 10.88.164.231:636.>
<Dec 7, 2013 12:22:53 AM IST> <Warning> <oracle.ods.virtualization.engine.backend.jndi.LDAP2.JNDIConnectionPool> <OVD-60024> <Connection error: simple bind failed: 10.88.164.231:636.>
<Dec 7, 2013 12:22:53 AM IST> <Error> <oracle.ods.virtualization.engine.backend.jndi.LDAP2.BackendJNDI> <OVD-60143> <[#LDAP2] Unable to create connection to ldap://[10.88.164.231]:636 as null.
javax.naming.CommunicationException: simple bind failed: 10.88.164.231:636 [Root exception is javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty]
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:195)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2720)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:296)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at oracle.ods.virtualization.engine.backend.jndi.JNDIConnectionPool.createCtx(JNDIConnectionPool.java:463)
at oracle.ods.virtualization.engine.backend.jndi.JNDIConnectionPool.create(JNDIConnectionPool.java:494)
at oracle.ods.virtualization.engine.backend.jndi.JNDIConnectionPool.<init>(JNDIConnectionPool.java:156)
at oracle.ods.virtualization.engine.backend.jndi.RemoteServer.getJNDIConnectionPool(RemoteServer.java:163)
at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.getLDAPContext(BackendJNDI.java:984)
at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.getConnection(BackendJNDI.java:927)
at oracle.ods.virtualization.engine.backend.jndi.ConnectionHandle.getHolder(ConnectionHandle.java:415)
at oracle.ods.virtualization.engine.backend.jndi.ConnectionHandle.search(ConnectionHandle.java:250)
at oracle.ods.virtualization.engine.backend.jndi.JNDIEntrySet.initialize(JNDIEntrySet.java:219)
at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.get(BackendJNDI.java:728)
at oracle.ods.virtualization.engine.chain.Chain.nextGet(Chain.java:303)
at oracle.ods.virtualization.engine.chain.BasePlugin.get(BasePlugin.java:89)
at oracle.ods.virtualization.engine.chain.Chain.nextGet(Chain.java:314)
at oracle.ods.virtualization.engine.chain.BasePlugin.get(BasePlugin.java:89)
at oracle.ods.virtualization.engine.chain.plugins.usermanagement.UserManagement.get(UserManagement.java:742)
at oracle.ods.virtualization.engine.chain.Chain.nextGet(Chain.java:314)
at oracle.ods.virtualization.engine.chain.PluginChain.runGet(PluginChain.java:211)
at oracle.ods.virtualization.engine.chain.PluginManager.runGet(PluginManager.java:351)
at oracle.ods.virtualization.engine.chain.PluginManager.runGet(PluginManager.java:316)
...more
Caused By: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1731)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1692)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1675)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1601)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:94)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:414)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:387)
at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:332)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:190)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2720)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:296)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at oracle.ods.virtualization.engine.backend.jndi.JNDIConnectionPool.createCtx(JNDIConnectionPool.java:463)
at oracle.ods.virtualization.engine.backend.jndi.JNDIConnectionPool.create(JNDIConnectionPool.java:494)
at oracle.ods.virtualization.engine.backend.jndi.JNDIConnectionPool.<init>(JNDIConnectionPool.java:156)
at oracle.ods.virtualization.engine.backend.jndi.RemoteServer.getJNDIConnectionPool(RemoteServer.java:163)
at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.getLDAPContext(BackendJNDI.java:984)
at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.getConnection(BackendJNDI.java:927)
...more
Caused By: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
at sun.security.validator.PKIXValidator.<init>(PKIXValidator.java:57)
at sun.security.validator.Validator.getInstance(Validator.java:161)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.getValidator(X509TrustManagerImpl.java:108)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:204)
at oracle.ods.virtualization.engine.util.OVDTrustManager.checkServerTrusted(OVDTrustManager.java:99)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1198)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:136)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:925)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1170)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:637)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:89)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
Let us know for any helpful pointers on this
Thanks in advance,
RPB25

Use the steps given below to perform import public key certificate of AD into OIM envirioment for SSL
Obtain the AD Certificates from the AD Administrator.
Copy the AD Certificates to the directory /jrockit-jdk1.6.0_20/jre/lib/security
Run the following command to import all the certificates
/jrockit-jdk1.6.0_20/bin/keytool -import -alias <provide_alias> -file <file-name> -keystorecacerts -storepasschangeit
4. The CA certificates are now present in the trust store.

How to create different log files for different levels

Hi,
Can some one please help me with my problem I have here?
I want to send log data to two diffrent files depending on the logging level such as DEBUG and WARN using the same logger instance.
How can you configure this in log4j.properties.
Please post sample code for log4j.properties to achieve this.
Thanks in advance.
Anurag SIngh

Hi,
I have tried your code. the issue is other log file for error is blank. its not writting log to that file.
following is the code of my log4j.properties
Please read the code first
# Set root logger level to DEBUG and its only appender to A1.
log4j.rootCategory=DEBUG,A1
#Appender and its layout for A1
log4j.appender.A1=org.apache.log4j.FileAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %log4j.appender.A1.Threshold=DEBUG
log4j.appender.A1.File=./LogonApplication_Debug.log
log4j.appender.A1.Append=true
#Appender and its layout for A2
log4j.appender.A2=org.apache.log4j.FileAppender
log4j.appender.A2.layout=org.apache.log4j.PatternLayout
log4j.appender.A2.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %
log4j.appender.A2.Threshold=ERROR
log4j.appender.A2.File=./LogonApplication_Error.log
log4j.appender.A2.Append=true
In my logger class i have written something like this:
public static Logger myLogger = Logger.getLogger (LoggerTest.class.getName());
     public static void main(String args[]){
          myLogger.debug("I have logged a debug message");
          myLogger.error("I have logged an error message");
Issue:
Now the problem is that it is creating two files specified in the configuration but it is logging messages both the messages debug and error in only ./LogonApplication_Debug.log file.
Though it is creating the ./LogonApplication_Error.log file, but it is only blank.
Can you please trace whats missing/wrong.
Thanks a lot.
Shanu

Accounts that have not been logged into for more than 90 days

Hi Folks,
Good Day.
Can anyone help me to update below powershel script?
below script find in my domain all the AD users accounts that have not been logged into for more than 90 days and export the report to .csv file. in addition what I want:
1. OU=Others, Sales --> exclude this OUs
2. Disable all the user based on 90 days export report .csv file
import-module activedirectory
$domain = "test.com"
$DaysInactive = 90
$time = (Get-Date).Adddays(-($DaysInactive))
$timer = (Get-Date -Format yyyy-mm-dd)
# Get all AD User with lastLogonTimestamp less than our time and set to enable
Get-ADUser -Filter {LastLogonTimeStamp -lt $time -and enabled -eq $true} -Properties LastLogonTimeStamp |
# Output Name and lastLogonTimestamp into CSV
select-object givenname,Name,@{Name="Stamp"; Expression={[DateTime]::FromFileTime($_.lastLogonTimestamp).ToString('dd-MM-yyyy_hh:mm:ss')}} | Export-Csv c:\temp\90DaysInactive-$(Get-Date -format dd-MM-yyyy).csv –NoTypeInformation
Many thanks for advance Help:

Hi Anna,
Good Day.
Many thanks for your responce.
with your help i can manage to exclude the OUs as wellas can get the .csv report via mail.
Now i want to disable all the user based on 90 days export report .csv file.
could you help me on this please? the report will come everyday like below:
filename=90DaysInactive-dd-mm-yyyy.csv
sample output:
Given name User Name
Last LogOn
Test User1 user1
03-10-2006_05:30:59
Test User2 user2
02-10-2006_12:00:34
import-module activedirectory
$domain = "test.com"
$DaysInactive = 1
$time = (Get-Date).Adddays(-($DaysInactive))
$timer = (Get-Date -Format yyyy-mm-dd)
$FileName="c:\temp\90DaysInactive-$(Get-Date -format dd-MM-yyyy).csv"
$from = "[email protected]"
$to = "[email protected]"
$smtpHost = "smtpservername"
$Subject = "90 Days Inactive Accounts"
$body = "90 Days Inactive Accounts report"
# Get all AD User with lastLogonTimestamp less than our time and set to enable
Get-ADUser -Filter {LastLogonTimeStamp -lt $time -and enabled -eq $true} -Properties LastLogonTimeStamp | where {($_.distinguishedname -notlike "*OU=HR*") -and ($_.distinguishedname -notlike "*OU=OT*")} |
# Output Name and lastLogonTimestamp into CSV
select-object givenname,Name,@{Name="Last Logon"; Expression={[DateTime]::FromFileTime($_.lastLogonTimestamp).ToString('dd-MM-yyyy_hh:mm:ss')}} | Export-Csv c:\temp\90DaysInactive-$(Get-Date -format dd-MM-yyyy).csv -NoTypeInformation
Send-MailMessage -From $from -To $to -Subject $subject -cc $cc -SmtpServer $smtpHost -Attachments $FileName -Body $body -BodyAsHtml
Thanks for your advance help.

Using logging.properties in weblogic 10.3.6

Hi
I have created logging.properties under Middleware Home and the content of property file is below
####################Logging.properties file content####################
handlers = java.util.logging.ConsoleHandler,java.util.logging.FileHandler.level=INFO
# Handler specific properties.
# Describes specific configuration info for Handlers.
############################################################# default file output is in user's home directory.
java.util.logging.FileHandler.pattern =/apps/Oracle/debug.log
java.util.logging.FileHandler.limit = 10MB
java.util.logging.FileHandler.count = 10
java.util.logging.FileHandler.formatter =java.util.logging.SimpleFormatter
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
# Facility specific properties.
# Provides extra control for each logger.
# For example, set the com.xyz.foo logger to only log SEVERE
# messages:
oracle.oes.common.level=FINEST
oracle.jps.authorization.level=FINEST
oracle.jps.authorization.debugstore.level=FINESTThen I edited startWeblogic.sh under <domain_home>/bin and added the following entries to it.
if [ "${WLS_REDIRECT_LOG}" = "" ] ; then
echo "Starting WLS with line:"
echo "${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy
${JAVA_OPTIONS} -Djava.util.logging.config.file=/apps/Oracle/Middleware/logging.properties -Duser.home=/home/oracle ${PROXY_SETTINGS} ${SERVER_CLASS}"
${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS}
${PROXY_SETTINGS} ${SERVER_CLASS}
else
echo "Redirecting output from WLS window to ${WLS_REDIRECT_LOG}"
${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ->> Djava.util.logging.config.file=/apps/Oracle/Middleware/logging.properties -Duser.home=/home/oracle ${PROXY_SETTINGS} ${SERVER_CLASS} >"${WLS_REDIRECT_LOG}" 2>&1
fiI restarted weblogic server and was hoping to see the log file in the location i specified in logging.properties. But I couldn't see the log file being generated.
Any Help!!!

Hi,
The --component flag is missing.
Solution
Use the following command for Archiving Logs by File Size:
beectl> modify_property --component CURRENTsite:LoggingProperties name MaxFileSize value <log_file_size>
or
Use the following command for Archiving Logs by Directory Size:
beectl> modify_property --component CURRENTsite:LoggingProperties name MaxLogSize value <log_directory_size>
Regards,
Kal

Log.properties for OIM

Similar Messages

Maybe you are looking for