Configuring CIF application log in APO

Folks
I was trying to configure CIF Application log from an APO perspective by specifying a function module and the different table fields.
I configured the same in R3 side using CFC6 but am having trouble finding it in APO
Does any body know how to dod this in APO ?
Thanks

Thanks for the repsonse folks
I tried /SAPAPO/C41 with detailed option but failed to see the detailed log which I had enabled in R3 through CFC6.
In R3, I enabled field logging for function module CIF_PRODUCT_SEND. In R3 log, I am able to see the relevant fields form this function module that are being sent to APO.
However, I also want to see the log from APO, for the same fields, if they were recieved without any errors or sent to postprocessing.
There is a function module /SAPAPO/CIF_PROD and I need to use the fields of the modules in the APO side CIF logging.is this possible ?
Would appreciate if any one can share their thoughts on how this can be accomplished
Thanks

Similar Messages

CIF queues - Lock not possible error in application log

hi,
Below is the application error log from SLG1
Looks when R3 is sent CIF queue, could not be processed at APO, due to lock not possible. It looks, the object is already locked.
This happens only certain hours only. We searched in batch jobs etc across landscape, but no luck.
We are currently checking, if this could be due to some issues with LiveCache processing.
Any input would be helpful.
SLG1 - Application log errror:
Source system: sapapp80 user: R3CIFRFC transaction: function module: /SAPAPO/CIF_CLAF_INB
Access block: data from system CLAF updated again
Lock not possible for charc at FM claf_inb:000000000100020361G21C02244Z
Object is locked at present
Thanks,
RajkS

Hi Raj,
Pls check the table CIF_IMOD details in R3 System,if 2 IM running with the same object we use to get these kind of
locking issue.
also check the workprocesses details during those time. whether you have enough space to process the reqd the
t-data.
Regards
DPS

Configure CCMS alert to Analyze Application log

Hi ,
Please provide the prodecure to configure CCMS alert for Applications logs from SLG1 tcode.
If any error log(prefarably Important logs ) is created then a alert should be triggered .
Background : We are using Solution Manager 7.0 as Central monitor system for Satellite systems of verions ECC6.0.
Thanks & Regards
ganesh

this answer is no longer needed

Not able to cif transiton data from APO to R/3 and from R/3 to APO

Hi:
I have made all relevant setting as per required for configuration of cif architecture in R/3 and in APO.I am able to cif master data from R/3 to APO but when I am transferring Planned Order from APO to R/3 or Sales Order from R/3 to APO I am not able to tranfer it .Even I am not getting any blocked q.
Even I am able to access remote login to both system by RFC Connection.
Please let me know how to debug it and solve it.
With Regards
Ashish Gupta

Hi Ashish,
Please try ciffing only one transactional data and then check on the application logs using t-code CFM1 or SLG1 in R/3 and /n/sapapo/c3 & slg1 in APO. This will give you idea where is going on wrong.
Kindly confirm
Regards
R. Senthil Mareeswaran.

Error Message in portal application.log

Hi all,
There are error messages continually been written to application.log.
Here is the path.
$ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log
We couldn't find out what's wrong.
Portal Version is 10.1.2.2.0.
application.log
07/01/31 16:54:54 portal: [module=RepositoryServlet, ecid=103102642203,1] ERROR: Repository Gateway error: Request Processing Error:
maxlength.htc: PROCEDURE DOESN'T EXIST
07/01/31 17:23:44 portal: [module=RepositoryServlet, ecid=133169185626,1] ERROR: Repository Gateway error: Request Processing Error:
maxlength.htc: PROCEDURE DOESN'T EXIST
07/01/31 17:23:58 portal: Broken pipe
07/01/31 17:23:58 portal: Broken pipe
07/01/31 17:23:58 portal: id=146054097151,1 Exception processing portlet response
java.lang.ArrayIndexOutOfBoundsException
     at java.lang.System.arraycopy(Native Method)
     at com.evermind.server.http.EvermindServletOutputStream.write(EvermindServletOutputStream.java:216)
     at com.evermind.server.http.EvermindServletOutputStream.write(EvermindServletOutputStream.java:151)
     at oracle.webdb.repository.service.RepositoryHttpResponseWrapper$RepositoryOutputStreamWrapper.write(Unknown Source)
     at oracle.webdb.page.CharConvertingOutputStream.write(Unknown Source)
     at oracle.webdb.page.v2.BaseDataProcessor.addToOutputStream(Unknown Source)
     at oracle.webdb.page.v2.BaseDataProcessor.includePortlet(Unknown Source)
     at oracle.webdb.page.v2.BaseDataProcessor.parseLayout(Unknown Source)
     at oracle.webdb.page.v2.BaseDataProcessor.assemblePage(Unknown Source)
     at oracle.webdb.page.v2.BaseDataProcessor.process(Unknown Source)
     at oracle.webdb.page.PageBuilder.process(Unknown Source)
     at oracle.webdb.page.Main.doRequest(Unknown Source)
     at oracle.webdb.page.ParallelServlet.doGet(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:834)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:340)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:260)
     at oracle.webdb.portal.servlet.PortalServlet.doGet(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:834)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:340)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:228)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
----------------------

$ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log
os the log of the "parent application". This is rather high level in the container. The message in the logfiles tells you that a procedure doesn't exist.
This can mean 3 things:
1. The procedure really doesn't exist
2. The procedure expects different parameters then passed
3. In the procedure a specific array member is called (but not found). (don't know how to explain this better in English, sorry for that).
It has been a while since I touched portal. In the past portal used a DAD (located in your HTTP-Server configuration). By changing the error style of the dad, you might find a more comprohensive error message.

Domain user no longer exists but getting errors in application log

Hi,
We had a domin user with which SQL service and SQL agent is configured to start. But this account does not have access to that server in which SQL is installed now. I can see the follwing message in application log:
Log Name:      Application
Source:        MSSQLSERVER
Date:          3/10/2014 2:00:00 PM
Event ID:      18456
Task Category: Logon
Level:         Information
Keywords:      Classic,Audit Failure
User:          Domain \username
Computer:      XXXX
Description:
Login failed for user 'Domain \username'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSSQLSERVER" />
    <EventID Qualifiers="49152">18456</EventID>
    <Level>0</Level>
    <Task>4</Task>
    <Keywords>0x90000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-03T04:00:00.000000000Z" />
    <EventRecordID>20420597</EventRecordID>
    <Channel>Application</Channel>
    <Computer>XXXXXXX</Computer>
    <Security UserID="S-1-5-21-2091904384-3689332406-323980668-6522" />
</System>
<EventData>
    <Data>domain\usernamer</Data>
    <Data> Reason: Failed to open the explicitly specified database.</Data>
    <Data> [CLIENT: <local machine>]</Data>
    <Binary>184800000E000000100000004100550030003400550041005000300036003800510041004E00380032000000070000006D00610073007400650072000000</Binary>
</EventData>
</Event>
How come this message is coming in the application log, since no one has tried to log in to the application?

Hi Both are 2008R2 version. My doubt is I can see that login failed message in application log but how to find out which process is trying to use that login?
First observe that this is something that runs on the same machine as SQL Server. (The error message says "CLIENT: <local machine>".) That may be a clue enough.
If not, set up a includes Audit: Login Failed and no other event. Of interest are the columns ApplicationNmae and the the column ClientProcessID. ApplicationName may be sufficient, but if not you can use ClientProcessID and match this against the PIDs you
see in Task Manager or Process Explorer. There is a risk it is a short-lived process and then you will have to look at Process Explorer and Profiler in parallel.
Erland Sommarskog, SQL Server MVP, [email protected]

Issue regarding application log in standard program RPCLMSU0

System Status: SAP ECC6, SP15.
This probem has been observed after we have upgraded from 4.6C.
In the include RPCLMSUF of the Report RPCLMSU0, there is an FM BAL_LOG_MSG_ADD, which adds messages to an application log.
A structure is passed to the FM, of type bal_s_msg.
The first 3 components of the structure are of type:
sy-msgt, sy-msgid and sy-msgno.
These should normally be filled in by values from the FM called just above it: BAL_LOG_CREATE.
But this doesnu2019t happen.
So, SAP has hardcoded values for these 3 as u2018Eu2019 (Message type), HRPAYNA_ALV (Message ID) and u2018998u2019 (Message no).
These are the values that get printed when the program is tested. i.e. the hardcoded text is getting displayed.
Output in the ALV : HRPAYNA_ALV:998 ***********No records found***********
We have checked the documentation for the FMs, and even gone through a few sample programs that SAP has created like SBAL_DEMO_02. The output is perfect here.
Since this is code that SAP has added (Entire form added "SL0K008292) by SAP to its standard code, they must believe that these hardcoded text will still not get printed. Can this error can be corrected by making some configuration changes in the system (SLG1?).
The code of the suroutine where this FM is called is given below:
FORM alv_appl_msg_add USING iv_text1 TYPE any
                            iv_text2 TYPE any
                            iv_text3 TYPE any
                            iv_text4 TYPE any.
Constants delcation.....
CONSTANTS: lc_msgid TYPE sy-msgid VALUE 'HRPAYNA_ALV', " Message ID
             lc_msgty TYPE sy-msgty VALUE 'E'. " Message Type
Data declarations.....
DATA ls_msglog TYPE bal_s_msg.      " Structure for msg log
ls_msglog-msgty     = lc_msgty.
ls_msglog-msgid     = lc_msgid.
ls_msglog-msgno     = gv_msgno.
ls_msglog-msgv1     = iv_text1.
ls_msglog-msgv2     = iv_text2.
ls_msglog-msgv3     = iv_text3.
ls_msglog-msgv4     = iv_text4.
Function module is used to add the messages to message log
CALL FUNCTION 'BAL_LOG_MSG_ADD'
    EXPORTING
      i_s_msg = ls_msglog
    EXCEPTIONS
      OTHERS = 1.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.                               " IF sy-subrc <> 0
ENDFORM.                               " alv_appl_msg_add

Hi
Pass IDoc Number, Date, Time from EDIDC table to FM-
'APPL_LOG_READ_DB'.
You'll get all log details of that IDoc.
For only Message, check FM - 'IDOC_GET_MESSAGE_ATTRIBUTE'.
Regards.

How to restore a filestream enabled and rbs configured web application

HI
in sharepoint farm I taken backup of a filestream enabled and rbs configured web application from central admin
and how to restore it in a new sharepoint farm in different server
adil

hi i seen this error message in sprestore file in restore foloder,
i am trying to restore the backup in sql srver 2008 R2
and
backup taken by sharepoint form which has back end sql server 2010 database datacenter
IF EXISTS ( SELECT * FROM master..sysdatabases WHERE has_dbaccess(name)=1 AND
name=@db_name )
BEGIN
SELECT 1 as ErrorCode
END
ELSE
BEGIN RESTORE DATABASE [WSS_Content_Prod] FROM
DISK=@db_location WITH STATS=5, FILE=1, MOVE @db_OldName TO @db_NewFile, MOVE @db_OldLogName TO @db_NewLogFile, MOVE @fsfg_old0 TO @fsfg_new0, NOREWIND, NOUNLOAD, RESTART, RECOVERY
END
@db_location=C:\BackUpandRestore from 117\ALPROD\spbr0000\0000016A.bak, @fsfg_old0=RBSFilestreamFile, @fsfg_new0=c:/rbs, @db_OldName=WSS_Content_Prod, @db_NewFile=C:\Program Files\Microsoft
SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content_Prod.mdf, @db_OldLogName=WSS_Content_Prod_log, @db_NewLogFile=c:/Prodlogs\WSS_Content_Prod_log.ldf, @db_name=WSS_Content_Prod
[3/24/2014 9:44:08 PM] Verbose: [WSS_Content_Prod] SQL command timeout is set to 1.00 hours.
[3/24/2014 9:44:08 PM] FatalError: Object WSS_Content_Prod failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SqlException: The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
RESTORE DATABASE is terminating abnormally.
[3/24/2014 9:44:08 PM] Debug: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreHelper.RunCommand(SqlCommand sqlCommand, SPBackupRestoreInformation args, Boolean throwOnRestart, Boolean& restart, SPSqlBackupRestoreConnection connection)
at Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreHelper.Run(SPBackupRestoreInformation args)
at Microsoft.SharePoint.Administration.Backup.SPSqlRestoreHelper.Run(SPBackupRestoreInformation args)
at Microsoft.SharePoint.Administration.SPDatabase.OnRestore(Object sender, SPRestoreInformation info)
at Microsoft.SharePoint.Administration.SPContentDatabase.OnRestore(Object sender, SPRestoreInformation info)
[3/24/2014 9:44:08 PM] Verbose: Starting OnPostRestore event.
[3/24/2014 9:44:08 PM] Verbose: Starting object: SharePoint - 85.
[3/24/2014 9:44:08 PM] Progress: [SharePoint - 85] 100 percent complete.
[3/24/2014 9:44:08 PM] Verbose: [SharePoint - 85] Restoring features and its activation properties.
adil

RFC destination with CIF application case !

Hi,
Can someone explain the difference between
Assigning a logical system to a RFC destination and
u201CAssigning a logical system to a RFC destination with CIF Application case" (there are 4 of them in all as i see - AC, RL, RQ, DG, AC- refers to availability check)
e.g I have 2 entries in the system landscape settings.
1) Logical system u2013 RFC destination
2) Logical system- application case AC u2013 RFC destination.
Even if I remove the 2nd entry, the relevant APO ATP FMu2019s are called (just a negative testing to see what goes wrong without application case) but am clueless about this concept of CIF application case. Why such a provision to begin with. The context help says. some transaction need to have synchrious RFC and hence the need but i see the same even without his entry.
Regards,
Loknath

Hello Loknath,
If I understand your query correctly,
1.Assign logical system to RFC destination is OK for you.
2.Assigning the RFC destination to a specific CIF application is used in the following case,
You have a system/service user set up for communicating with the R/3 system thru CIF & this is assigned to the RFC destination assigned to the point no:1
& for debugging purposed you need a dialogue user, so you may assign this dialogue user to a different RFC destination & assign it here in the customizing (Assign RFC to application cases) to the application Debugging..so that while the particulat application is called (Debugging...CIF cockpit...etc)the corresponding settings from the different RFC destinations will be used.
I could not understand your query, where u relate some ATP stuffs with this CIF topic...
Thanks,
Mahesh

XI 7.0 NW 2004s install - JMS Errors in applications.log & defaultTrace

We just installed XI 7.0 NW 2004s. The installation of XI 7.0 NW 2004s is a lot simpler than XI 3.0 NW 2004 since the Template installer runs most of the post installation steps.
However, there are a few issues that I am encountering that i did not see with XI 3.0 installations. The installation is on Windows 2003 server and SQL server 2005.
Checking the applications.log file through Visual Administrator LogViewer, I see that the Applications log is filing up every few seconds with the following repeating errors:
Message -
Exception on server occured! Internal error.
Additional Information -
Category : /Applications/JMS
Message ID : 001422B146E800750000070D0000013000041A845FCB659B
Source Name : /Applications/JMS
Thread : SAPEngine_Application_Thread[impl:3]_26
Application :
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : d16ec30026fd11dbb450001422b146e8
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : com.sap.jms.client.session.Session
Resource Bundlename :
Session : 0
Source : /Applications/JMS
ThreadObject : SAPEngine_Application_Thread[impl:3]_26
Transaction :
User : J2EE_GUEST
Message -
Exception on server occured! Cannot write to transaction log TXf48.tx.
Additional Information -
Category : /Applications/JMS
Message ID : 001422B146E800750000070A0000013000041A845FCB4CC8
Source Name : /Applications/JMS
Thread : SAPEngine_Application_Thread[impl:3]_26
Application :
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : d16ec30026fd11dbb450001422b146e8
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : com.sap.jms.client.session.Session
Resource Bundlename :
Session : 0
Source : /Applications/JMS
ThreadObject : SAPEngine_Application_Thread[impl:3]_26
Transaction :
User : J2EE_GUEST
In the defaultTrace.trc file, i see the JMS error too:
Message -
Error From List = javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:1808)
     at com.sap.jms.client.session.Session.rollback(Session.java:300)
     at com.sap.jms.client.session.Session.close(Session.java:158)
     at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
     at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:262)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:361)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Additional Information -
Category : /Version
Message ID : 001422B146E8008B000007340000013000041A847A0F6CB9
Source Name : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession
Thread : SAPEngine_Application_Thread[impl:3]_98
Application :
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : d815880126fe11db9edc001422b146e8
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : /Version
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession
ThreadObject : SAPEngine_Application_Thread[impl:3]_98
Transaction :
User : J2EE_GUEST
This is filing up both the applications.log and defaultTrace files. I cannot find any information through Service Marketplace. Has anyone encountered this issue? This is new installation - no messages are running on it so I am not sure why there is a JMS error.
Regards,
Jay

Hi Jay,
The exception means that the JMS Provider is not able to write to the transaction log file upon close of a transacted session. In NW04s, JMS transactions are stored as files on the local file system. The location of the root folder where the transactions are persisted is configured by the JMS service property "transactionStorePath". You can check its value through the Visual Administrator -> Services-> JMS Provider -> Properties. Please check if it contains a correct directory path and that nothing prevents the server from writing to this path - access rights, enough disk space, etc. If there is something wrong with the path, you can change it, save the change and restart the JMS provider service for the change to become effective.
You can also have a closer look at the server trace file: the root cause of the above exception is some other exception, probably I/O one, and it should be logged somewhere in adjacency to the JMS exception.
There is ongoing JMS communication even in a new server installation - in this case (judging from the stack trace) the component that performs this JMS activity is the timeout service.
Hope this helps,
Stoyan

PrintStackTrace not appearing in application.log?

We are having a difficult time locating the Stack Traces that we expected to see in the application.log of our J2EE Web Applications. Within our servlets the typical try/catch sequence is something like:
try {
// do some stuff that can throw an exception
} catch(Exception ex) {
ex.printStackTrace();
ErrorBean errorBean = new ErrorBean(
(ex.getMessage()!=null) ? ex.getMessage() : ex.getClass().getName(),
request.getRequestURI(),ex);
// Push ErrorBean into request scope for forward to Error Handler
request.setAttribute(Constants.ERROR_KEY,errorBean);
return (mapping.findForward("unexpectedError"));
However, we can't find the output from the ex.printStackTrace() anywhere. It doesn't appear to be laying in the application.log. Any ideas? Is there something we should configure somewhere to send the stacktraces to application.log?
Arghh....any help would be greatly appreciated.
Bob
Bob

Ah...yes...they were right where you said they would be. However, is there some configuration that I could do to put the console messages (System.out.println() and, more importantly for us, ex.printStackTrace()) in the global-application.log so we would at least get some concept of the time of the exceptions? As it stands now we can see the actual exceptions in a file named after our OC4J instances (./ora9ias/opmn/logs/camsu.default_island.1) and some logging stuff with Timestamps from the Struts framework in the file the application.xml sends it to(<file path="../log/global-application.log"/>) but it is difficult to match the exceptions up with the servlet requests that caused them due, mainly, to lack of timestamps. Is there a way to get the stuff that presently goes to the opmn/logs file into the global-application.log?
Regardless, I will definitely follow up the the Log4J stuff. Maybe that's where the magic bullet is. Thanks so much for your reply. This was giving me fits.
Bob

Can I rotate application log in OC4J_Portal_default_island_1?

My application.log file in %oracle_home%\j2ee\oc4j_portal\application-deployments\portal\oc4j_portal_default_island_1 grows quickly. Can I configure it to rotate every day or when it reaches a certain size? If yes, how?
TIA
Edited by: Angrydot on Aug 25, 2008 9:51 PM - what happens if I edit an old post in the new forum?
Edited by: Angrydot on Aug 25, 2008 9:52 PM - nothing

To rotate the OC4J log files under $ORACLE_HOME/opmn/logs, there are few parameters you can modify that are not documented in Oracle 9.0.4/10.1.2 documentation.
[New JVM parameters]
"stdstream.filesize"
Max file size limit of each archive. Unit is megabyte.
"stdstream.filenumber"
Max number of files that oc4j can keep as archives. The oldest file will be automatically deleted if the limit is exceeded.
[Usage]
ex 1: rotate stdout/stderr when the file size is reached to 2.5M byte.
java -Dstdstream.filesize=2.5 -jar oc4j.jar -out std.out -err std.err
OraHome\opmn\conf\opmn.xml
In order to get these parameters in opmn.xml you need to define it as follows:
<category id="start-parameters">
<data id="java-options" value="-server -Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless =true -Dstdstream.filesize=0.2 -Dstdstream.filenumber=5"/>
<data id="oc4j-options" value="-out std.out -err std.err"/>
</category>
The new log files will be created under:$ORACLE_HOME\j2ee\home\home_default_island_1\
The file naming will be like:
std_2006_02_22_14_01_17.out
std_2006_02_22_14_16_25.out
Important notes:
1. Backup opmn.xml file before any modification.
2. Modify opmn.xml file to specify stdstream.filesize and stdstream.filenumber. See the example above.
3. Test and validate this solution in your test system first before implementing in Production.

Weblogic 8.1 (SP4) configuration for console log

Weblogic version: 8.1 SP4
By default in console (cmd window) log, date and time format is as below.e.g
<Jul 11, 2008 12:22:35 PM IST>
I need to see time in millisecond. Is there any configuration for this?
please help.

Assuming the log entries you care about are generated by your application, and not the infrastructure, you're better off adding millisecond detail to your application log messages. If you're using commons-logging, you can tie this to the WL server log implicitly through configuration, or you could use NonCatalogLogger to explicitly log to the WL server log.

Purging application logs automatically under Weblogic servers

Hi,
I am trying to explore purging options in Weblogic server.
Could someone help me in finding a setting(if there is one) under Weblogic properties files, which will purge Application logs automatically after 'n' number of days.
for example in D:\Hyperion\deployments\WebLogic9\servers\aas\logs directory, I see a lot of eas log files created with extensions from .log00001 to .log00427. Is there any way of removing these automatically without using any other windows scripts.
Thanks
Prasad

This is configured within each server's Logging tab ( Servers -> server_name -> Logging ). Set the rotation type to "Time", files to retain, and rotation interval ( default 24 hours ), etc. This will keep the files to a fixed count.

Messages from IDoc processing can be found in application log

We are using the IDOC_INPUT_INVOIC_MRM Function Module to post Inbound Vendor EDI Invoices. During testing, we sometimes see the error "Messages from IDoc processing can be found in application log". We then have to check transaction SLG1 to ascertain the 'real' issue, e.g. "No GR documents found". In a Production environment however, this will be very inconvenient. Our business users process their own iDoc errors according to the iDoc Status, so to have to call up another transaction, and select the correct Application Log to find the true error, is not a process I would feel comfortable with for our users.
My question is, can we configure/determine which messages are passed to the iDoc Status, or redirect Application Log messages ? Might a Z version of FM IDOC_INPUT_INVOIC_MRM be the way forward ?
Many thanks,
Paul.

Hi,
Just monitor your error idocs in WE20 transaction. Give idoc number here then execute, you can see the all three records(control, data, status). Click on status record node then double click
on status number(e.g 51), it will take you to another screen there you click on "application log" button on application toolbar. This is the standard way finding the application log of an idoc, even i am finding the application log on production server like this.
Thanks,
Asit Purbey.

Configuring CIF application log in APO

Similar Messages

Maybe you are looking for