How to start the file server for Agile PLM

when i try to add one attachment for an Item, i got the following error message:
The preferred file server http://agileserver:8080/Filemgr/AttachmentServlet for user : xxx is down
how to startup the file mgr?

Hi is this looks like a question for Agile A9.
For Agile A9 or Primavera questions, you can use Oracle Support, Support Communities, Yahoo Groups for Agile API or WRAU.
This forum is for Agile PLM for Process, which is part of the same Agile family but a different product.
Thanks.

Similar Messages

How to start the Message Server?

Hi,
I wish to start the J2EE engine and for the same it is mandatory to start the Message Server first.
In order to start the message server, I run the following command:
D:\usr\sap\J2E\SYS\exe\uc\NTI386>msg_server start
msg_server=>sapparam(1c): No Profile used.
msg_server=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
[Thr 7972] Wed Jul 25 23:39:18 2007
[Thr 7972] *** ERROR => MsSetWorkDir: chdir D:\usr\sap
D00\work [msntserv.c 170]
[Thr 7972] *** ERROR => MsSPrvInit: MsSetWorkDir [msntserv.c 87]
[Thr 7972] *** ERROR => mainU: MsSPrvInit [msxxserv.c 1634]
I gave my best time to search for Profile configuration details. But I could not do that.
Can somebody tell me how to start the Message Server?
regards,
Anand

Hi Anand,
Will be good to know what OS are you using...
If you're tryng to start an instance use <prompt>: startsap pf=<profile of the system you want to start>
If you logon as <sid>adm just type startsap
If for some reason you need to start only the message server try <prompt>: msg_server start pf=<profile of the system you want to start>
Regards
Juan
Please reward with points if helpful

How to start the oc4j server

I install oracle 9ias 9.0.3,but i don't know how to start the oc4j server.
thanks for any help?

hi
Refer "Starting and Stopping OC4J" from
http://otn.oracle.com/tech/java/oc4j/doc_library/902/A95880_01/html/toc.htm
hope this helps.
shrini

How to start the admin server on another WLS machine?

Hi,
          I have a weblogic cluster with 2 weblogic machines: machineA and machineB.
          The cluster contains 4 managed servers (2 on each WLS machine)
          The admin server runs on machineA (standalone).
          I have a file backup of the domain directory on machineA.
          Suppose machineA crashes.
          How can I start the admin server on machineB?
          Kind regards,
          Pieter

Thanks for your reply,
          I know how to (re)start the admin server on machineA. But in this case I want to start the admin server on machineB.
          The documentation says:
          Restarting an Administration Server on Another Machine
          If a machine crash prevents you from restarting the Administration Server on the same machine, you can recover management of the running Managed Servers as follows:
          Install the WebLogic Server software on the new administration machine (if this has not already been done).
          Make your application files available to the new Administration Server by copying them from backups or by using a shared disk. Your application files should be available in the same relative location on the new file system as on the file system of the original Administration Server.
          Make your configuration and security data available to the new administration machine by copying them from backups or by using a shared disk. For more information, refer to Directory and File Backups for Failure Recovery.
          Restart the Administration Server on the new machine.
          Simply starting the admin server on the other machine does not work because it tries to start the admin server on the ip address of the old machine.
          Edited by [email protected] at 05/10/2007 7:47 AM

How to start the osb server

Hi please help me on this

Hi Vijay,
Before starting the OSB Server i need small clarification,
While OSB Domain Creation what option ur selected i.e. either OSB Developer or Just OSB,
If ur Selected OSB Developer then,
goto Your Installation Directory Like Oracle-->Middleware-->User_Projects-->Applcations(Domains)-->Double Click on Ur Domain Name-->Double Click on StartWebLogic.cmd
If ur Selected only OSB then,u need to follow the below 2 steps
1) goto Your Installation Directory Like Oracle-->Middleware-->User_Projects-->Applcations(Domains)-->Double Click on Ur Domain Name-->Double Click on StartWebLogic.cmd
2) copy the Path like Oracle/Middleware/User_Projects/Applcations(Domains)/Servers,
open cmd and paste here, after that,
Oracle/Middleware/User_Projects/Applcations(Domains)/Servers/StartManagedWeblogic.cmd osb_server1&.
Hope it will help you.....
Regards,
Kiran

How to start the temp server

Hi experts
Whether it is possible to copy the data of all disk in SAP server to another standby server with different hardware configuration ( without installing SAP only copying data from one server to another server retaining the IP id and hostname same) i want to activate in the stanby server whee we coied the SAP datas. what is the procedure do as it is??
bala

hi ruchit
i will describe the full text here. the sap server the os is crashed. with the vendor we got the standby server and installed the OS and partitioned the disk in to three logical partition. now we have copied the data from crashed server to their respective disks. now i want to start / initiate the server which data has been dumped from the old one. at present we want recover the SAP by some sort of settings / registries so to avoid the New SAP installation time.Here i need that how to enable all the services from this dump and make the SAP work. where we have maintained the Hostname and IP address is the same. could u tell me the steps involved in it.
bala

How to open the file writer for next entry after stream is close?

import java.io.BufferedWriter;
import java.io.FileWriter;
import java.io.IOException;
import java.util.Scanner;
public class TryOut {
     public static void main(String args[]) throws IOException{
          int inputQuestionnAireNum = 0;
          int inputPostCode = 0;
          int inputGender = 0;
          int inputAge = 0;
          int x=0;
          Scanner input = new Scanner(System.in);
          FileWriter fwrite = new FileWriter("tryout.txt", true);
          BufferedWriter out = new BufferedWriter(fwrite);
          boolean invalidNum = false;
          do{
               System.out.print("1 new entry or 0 print");
               x = Integer.parseInt(input.nextLine());
               if(x == 1)
                  //Questionnaire Number
                    System.out.print("Enter Questionnaire Number [ ] ");
                    inputQuestionnAireNum = Integer.parseInt(input.nextLine());
                    out.write("NumBER OF Q: "+inputQuestionnAireNum+", ");
                    //Postal code
                    System.out.print("Enter Postal Code [ ] ");
                    inputPostCode = Integer.parseInt(input.nextLine());
                    out.write("PostCode: "+inputPostCode+", ");
                    //Age
                    System.out.print("Enter Age [ ] ");
                    inputAge = Integer.parseInt(input.nextLine());
                    out.write("Age: "+inputAge+", ");
                    //Gender
                    System.out.print("Enter Gender '1' for Male and '2' for for female [ ] ");
                    inputGender = Integer.parseInt(input.nextLine());
                    out.write("Gender: "+inputGender+", \n");
                    out.close();
                       } while(x != 0);
     Result:
1 new entry or 0 print1
Enter Questionnaire Number [ ] 2
Enter Postal Code [ ] 1
Enter Age [ ] 3
Enter Gender '1' for Male and '2' for for female [ ] 4
1 new entry or 0 print1
Enter Questionnaire Number [ ] 2
Exception in thread "main" java.io.IOException: Stream closed
     at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:98)
     at java.io.BufferedWriter.write(BufferedWriter.java:203)
     at java.io.Writer.write(Writer.java:126)
     at TryOut.main(TryOut.java:31)
Hi, how can i open the file writer stream again for next entry after it is has been closed? if i do not close(); all my entry will not be recorded to the text file. how can i solve this ?
Edited by: metaroot on Feb 18, 2008 6:39 PM

The short answer to your question: use out=new BufferedWriter(fwrite) inside the do loop as well.The only difference that would make would be to make the problem worse. It is poor practice. Stream stacks should be constructed once for the life of the stream.
What he needs to do is close his stream outside the loop, possibly calling flush() where he presently has close().
The more relevant answer is: Why are you not wrapping the user-friendly PrintWriter class, wrapping it around the BufferedWriter?Possibly because he doesn't like the fact that PrintWriter swallows exceptions? which makes it less user-friendly IMO.
The println and print methods are very useful, and do not need closing between loop iterations.Neither does anything else.
By the way,you say that without a close() the BufferedWriter doesn't output to the file.I don't know: I never used/tried it.Even if it doesn't, it will surely output after you come out of the loop.If you don't want to use a PrintWriter, why don't you investigate this?Posting guesses here isn' t really much help, especially about something you've never used. A BufferedWriter has a buffer and it doesn't write anything until the buffer is full, you flush it, or your close it.

[solved] how to start the rabbitmq-server with systemctl

I got the rabbitmq package from https://aur.archlinux.org/packages/rabbitmq/. Upon installing with 'pacman -U', I got the message
==> WARNING:
==> This systemd unit executes rabbitmq as rabbitmq user. This is *DIFFERENT*
==> from the legacy sysvinit scripts included in the package that
==> default on using the "root" user. DO NOT MIX usage of this systemd unit
==> with rc.d initscripts, or permission problems may arise.
==> To fix those, use the following command (as root):
chown -R rabbitmq.rabbitmq /var/lib/rabbitmq
==> DO NOT DELETE anything manually, that may make your rabbitmq install
==> unusable, until deletion of everything under /var/lib/rabbitmq
I did the 'chown' thing as advised, but I'm not sure if there is something more I should be doing (or not doing).
I can start the server with
sudo rabbitmq-server
and then in another terminal I can do
sudo /usr/sbin/rabbitmqctl status
and the output seems to show everything working.
The trouble starts if instead of directly running rabbit-server, I do
sudo systemctl enable rabbitmq
sudo systemctl start rabbitmq
It seems to start fine and then I get (when I do systemctl status rabbitmq)
rabbitmq.service - RabbitMQ Messaging Server
Loaded: loaded (/usr/lib/systemd/system/rabbitmq.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2014-12-29 02:03:25 GMT; 4s ago
Process: 25657 ExecStop=/usr/bin/rabbitmqctl stop (code=exited, status=2)
Process: 25549 ExecStart=/usr/bin/rabbitmq-server (code=exited, status=1/FAILURE)
Main PID: 25549 (code=exited, status=1/FAILURE)
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: * epmd reports: node 'rabbit' not running at all
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: no other nodes on brunnhilde
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: * suggestion: start the node
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: current node details:
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: - node name: 'rabbitmqctl-25657@brunnhilde'
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: - home dir: /var/lib/rabbitmq
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: - cookie hash: 59JWXfWlAKuxru4vaTbvBQ==
Dec 29 02:03:25 brunnhilde systemd[1]: rabbitmq.service: control process exited, code=exited status=2
Dec 29 02:03:25 brunnhilde systemd[1]: Unit rabbitmq.service entered failed state.
Dec 29 02:03:25 brunnhilde systemd[1]: rabbitmq.service failed.
I presume this failure has something to do with the systemd warning that I got when installing, but I am not really sure what to do.
Has anyone got rabbitmq server working using systemctl?
Last edited by mjandrews (2014-12-29 20:25:13)

I seem to have fixed it now.
I changed /etc/rabbitmq/rabbitmq-env.conf from
NODENAME=rabbit
NODE_IP_ADDRESS=0.0.0.0
NODE_PORT=5672
LOG_BASE=/var/log/rabbitmq
MNESIA_BASE=/var/lib/rabbitmq/mnesia
to
NODENAME=rabbit
NODE_IP_ADDRESS=127.0.0.1
NODE_PORT=5672
HOME=/var/lib/rabbitmq
LOG_BASE=/var/log/rabbitmq
MNESIA_BASE=/var/lib/rabbitmq/mnesia
and that seems to have done the trick.

How to start the X server from console

In solaris 10 once we logged in cosole session is there any possibility to go to CDE or Java Mode
Without Log out.
Regds
Suseendran .A
919213540324

Hello.
Yes, this is possible (perhaps root access is needed).
However it is rather difficult...
I would try to write an own xinit script...
Martin

Configuring the file server in KM and access,edit the documents from it

Hi friends,
My requirement is to configure the file server where u will have all the structured and unstructured data stored here. So users can share the documents and create, edit ,save the documents from the file server itself.
In KM what kind of file servers are there apart from the one it supports by default.
Can anybody pls provide the configuration steps regarding how to configure the file server i KM.
To configure the file server is webDAV protocol required?
Points would be assigned for the helpful answer.
Thanks in advance.
Regards
Sireesha.

Dear Sireesha,
Well KM supports mostly all the File server however we have some restrictions with Novell FS and Sharepoint Server from Microsoft. Like versions and other meta data have some issues.
Alsothough to configure a File Server you need to first create a FS repository Manager. Details can be found in the help guide:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/e3/92322ab24e11d5993800508b6b8b11/frameset.htm">FS Repository Manager</a>
Yes WebDAV protocol is required here.
You can create WebDav RM as well.
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/4a/217fb6c33c6748a1715a161ac942cd/frameset.htm">WEBDAV</a>
The above links will help answer your queries.
Regards
Anjali

Adequate File Server for Design Studio

I am looking for feedback on the new mac mini. Hopefully, there are a number of you who have experience in the matter.
My company will soon have several designers on staff. Currently, my Mac Pro is serving as the file server for the company. This is not ideal, as I would like to use my Mac Pro as a work station. We have a ReadyNAS in the office, but it's sluggish performance would never hold up with our work flow. I need a file server that can handle less than 10 designers working on large files. Ideally, I would also like to find something that acts as an in-house web server.
The new Mac Mini with Thunderbold looks like it could fit the bill, but I would love to hear from people who are using the machine in a similar setup. Could the mini provide adequate performance as a file server? If so, what upgrades should I consider?
I am also looking at attaching the LaCe Little Big DIsk for the files. If I understand correctly, this should run as quickly as an internal drive, correct?
I would love to hear your feedback and any alternative suggestions.

I recently purchased a Mac Mini i& 2.0 with 7200RPM Drives and a Promise Pegasus R6 12TB File Server.
Everything worked great for 48 hours, but then my Pegasus Server droped a drive... Promise is RMAing me a replcement drive, but that takes about a week to get... I have heard issues with Promise RAIDs coming with 1 Bad drive, but I thought I was safe since I didn't have one after the 6 hour initialization process. The new drive wil be here by Friday, and hopefully I can do some tests on this thing to see if anything else goes wrong before the "Return/Refund" date is up. I really can't afford to have a $2,000 RAID PaperWeight.
I also asked Promise if I could simply go to "Best Buy" and get a replacement drive to get me back up and going (even though the server is still running I am apprehensive about using it without a "Redundant drive"), Promise said that the server will only work with "Apple Approved" drives, and only Promise can ship though drives, so I could not just go get a 2TB 7,200 RPM drive and replace the defective one myself.
Not sure there is any truth to this, but since the parts are under warranty for 2 years, I guess it doesn't matter as its not costing me anything but time and from using the new $2K server.
I thought about Drobo Pro servers too, but the reviews of them seemed 10 times worse that what I read about the Promise Servers.
Anyone out there has these R6 Pegasus Servers, care to comment? Should I cut my loses and return this thing or should I stick it out?

Reg:: How to Integrate the RMS server to open source word, excel, powerpoint

Hi Techys,
Please help me,
How to integrate the RMS server for opensource word, excel, powerpoint.... etc
Many Thanks,
Madhu

Hi Madhu,
SharePoint 2010 supports AD RMS in the same manner as SP2007, check out the Windows Server AD RMS Deployment with Microsoft
Office SharePoint Server 2007 Step-By-Step guide. This is being updated for SP2010.
Also you can have a look at the blog:
http://www.sharepointindepth.com/integrating-ad-rms-with-sharepoint-2010/
http://www.microsoft.com/en-us/download/details.aspx?id=8832
Best Regards,
Eric
Eric Tao
TechNet Community Support

How to start the server. Urgent.

I mistakenly deleted the icon from the Start menu, to start the SAP IDES server in my laptop. How to start the server from any other path.
I installed it in E drive (2003 server). Database path is F drive.

Hi,
Check the following path
E:\Program Files\SAP\FrontEnd\SapGui
Here the actual Logon Pad file would be stored with name "SAPLOGON" or "SAPLGPAD".
Create another shortcut for above file on your desktop.
Best regards,
Prashant

Having trouble starting the J2EE Server... for hours and hours...

Hi:
I am having problem starting the J2EE Server.
I have looked through this page where lots of people had similar problem:
http://forum.java.sun.com/thread.jsp?forum=136&thread=468079
but the solutions provided there could not solve my problem...
My problem, specifically, is that when I try to start the sever, I get:
com.sun.enterprise.admin.servermgmt.DomainException: ...
CLI156 Could not start the domain domain1.
I am using Windows XP Professional on IBM ThinkPad X30.
Does anyone have some idea how to solve the problem?
Thanx!

bsankararao,
Thanks for the quick response. I am currently using the latest IE6.0 XPXP2 version and yes I doe have a successful start of the domain1 process. Here is the startup log for verification:
[#|2004-02-02T15:03:04.765-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-02T15:03:12.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-02T15:03:12.436-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-02T15:03:14.649-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-02T15:03:15.470-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-02T15:03:15.491-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-02T15:03:15.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-02T15:03:32.084-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-02T15:03:34.338-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-02T15:03:34.938-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-02T15:03:36.391-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-02T15:03:36.421-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|autoDeployment status dir missing, creating a new one|#]
[#|2004-02-02T15:03:36.451-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.471-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.481-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:38.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:38.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [MEjbApp]|#]
[#|2004-02-02T15:03:48.818-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:49.549-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 12728 msec, Total EJB Compiler Module Time: 10775 msec, Portion spent EJB Compiling: 84%
Breakdown of EJBC Module Time: Total Time for EJBC: 10775 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 10605 msec (98%), JAX-RPC Generation: 20 msec (0%),
|#]
[#|2004-02-02T15:03:49.750-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2004-02-02T15:03:50.571-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:51.292-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.029-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.309-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5688 msec, Total EJB Compiler Module Time: 4737 msec, Portion spent EJB Compiling: 83%
Breakdown of EJBC Module Time: Total Time for EJBC: 4737 msec, CMP Generation: 2674 msec (56%), Java Compilation: 1933 msec (40%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2004-02-02T15:03:56.339-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-02-02T15:03:56.810-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-02T15:03:57.210-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-02T15:03:57.461-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-02T15:03:57.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-02T15:03:57.721-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-02T15:03:59.924-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-02T15:04:00.315-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.355-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.936-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.946-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.966-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:00.986-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:01.266-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075755841276|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-02T15:18:13.512-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T15:18:13.522-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T15:18:39.119-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T15:18:39.119-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:27:40.443-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:41.174-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:27:49.076-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:49.076-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:31:57.022-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:31:57.022-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:32:08.869-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:32:08.869-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T20:00:22.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T20:00:22.424-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-03T08:30:22.556-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T08:30:23.808-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T08:30:23.998-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T08:30:26.422-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T08:30:27.143-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T08:30:27.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T08:30:27.253-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T08:30:31.509-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T08:30:33.462-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T08:30:33.963-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T08:30:34.914-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T08:30:36.036-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T08:30:37.027-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T08:30:37.428-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T08:30:37.618-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T08:30:37.638-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T08:30:37.798-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T08:30:39.901-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T08:30:40.202-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.242-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.402-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.412-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.442-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.452-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.732-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075818640752|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T08:48:32.383-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\domains\domain1\autodeploy\hello.war ] for autodeployment.|#]
[#|2004-02-03T08:48:33.785-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [hello]|#]
[#|2004-02-03T08:48:33.835-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [hello]|#]
[#|2004-02-03T08:48:34.606-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 1862 msec, Total EJB Compiler Module Time: 50 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 50 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 10 msec (20%),
|#]
[#|2004-02-03T08:48:34.807-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/hello]|#]
[#|2004-02-03T08:48:35.007-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T08:48:36.719-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-03T08:48:36.729-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\domains\domain1\autodeploy\hello.war.|#]
[#|2004-02-03T14:53:47.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T14:53:48.718-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T14:53:48.929-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T14:53:51.222-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T14:53:52.003-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T14:53:52.033-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T14:53:52.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T14:53:56.449-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T14:53:58.492-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T14:53:58.983-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T14:53:59.985-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T14:54:01.206-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T14:54:02.188-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T14:54:02.678-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T14:54:02.899-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T14:54:02.919-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T14:54:02.939-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T14:54:03.119-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T14:54:05.563-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T14:54:05.883-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:05.943-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:06.083-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.093-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.123-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.133-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075841646434|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T23:32:20.272-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T23:32:22.004-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T23:32:22.234-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T23:32:24.608-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T23:32:25.629-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T23:32:25.659-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T23:32:25.689-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T23:32:31.237-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T23:32:33.781-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T23:32:34.332-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T23:32:35.453-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T23:32:37.156-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T23:32:38.317-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T23:32:38.948-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T23:32:39.179-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T23:32:39.199-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T23:32:39.229-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T23:32:39.439-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T23:32:42.343-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T23:32:42.724-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.764-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.944-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.954-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.994-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.014-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.315-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075872763335|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-04T08:31:44.681-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02

How to see the file at the application server

HI TO ALL SDNERS ,
 THIS IS MY CODE WHERE TO CHECK THE DOWNLOADED FILE AT THE APPLICATION SERVER.IN TCODE AL11 I HAVE SEEN THERE IS NO FILE GETTING CREATED.WHEN TRANSFERRING THE SY-SUBRC VALUE IS ZERO.
Program Name : ZME11_BDC.
Title : PURCHASE INFORMATION RECORD LOAD PROGRAM
Program Objective : THIS PROGRAM READS IN THE PURCHASE
 INFORMATION FILE. IT CREATES A BDC SESSION TO
 USE TO LOAD THE PURCHASE INFORMATION RECORDS
 INTO SAP using the ME11 Transaction.
REPORT ZME11_BDC no standard page heading MESSAGE-ID ZHNC line-size 55.
 constants declaration
constants: c_x value 'X',
 c_sess type apqi-groupid value 'zcustomer',
 c_xd01 type tstc-tcode value 'ME11'.
 DECLARING VARIABLES
DATA: V_MSG(255),
 V_ERREC TYPE I,"NO OF FAILED RECORDS
 V_LINES."NO OF RECORDS
 FLAG DECLARATIONS
DATA: FG_DATA_EXIST VALUE 'X',"CHECK FOR DATA
 FG_SESSION_OPEN VALUE ''.
 STRUCTURES AND INTERNAL TABLE DECLARATIONS
TYPES :BEGIN OF TY_PIR,
 LIFNR TYPE EINA-LIFNR,
 MATNR TYPE EINA-MATNR,
 EKORG TYPE EINE-EKORG,
 WERKS TYPE EINE-WERKS,
 VERKF TYPE EINA-VERKF,"sales person
 TELF1 TYPE EINA-TELF1,"telephone
 URZLA TYPE EINA-URZLA,"country
 REGIO TYPE EINA-REGIO,"region
 APLFZ(5),"plan deleivery time
 EKGRP TYPE EINE-EKGRP,"purchase group
 NORBM(13),
 NETPR(13),
 END OF TY_PIR.
DATA : IT_PIR TYPE TABLE OF TY_PIR,
 WA_PIR LIKE LINE OF IT_PIR.
DATA: BEGIN OF IT_BDCDATA.
INCLUDE STRUCTURE BDCDATA.
DATA END OF IT_BDCDATA.
DATA : BEGIN OF IT_BDCMSG.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA END OF IT_BDCMSG.
 SELECTION SCREEN
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETER : FNAME TYPE RLGRAP-FILENAME.
SELECTION-SCREEN END OF BLOCK B1.
 AT SELECTION ON VALUE REQUEST
AT SELECTION-SCREEN ON VALUE-REQUEST FOR FNAME.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
 FIELD_NAME = ' '
IMPORTING
 FILE_NAME = FNAME.
 START OF SELECTION
START-OF-SELECTION.
PERFORM F_GET_DATA USING FNAME
 CHANGING IT_PIR.
PERFORM F_GENERATE_DATASET USING FNAME
 CHANGING IT_PIR WA_PIR.
*& Form F_GET_DATA
 text
 -->P_V_FNAME text
 <--P_IT_PIR text
FORM F_GET_DATA USING P_FNAME LIKE FNAME
 CHANGING P_IT_PIR LIKE IT_PIR.
DATA: LV_FILE TYPE STRING.
LV_FILE = FNAME.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
 FILENAME = LV_FILE
 FILETYPE = 'DAT'
HAS_FIELD_SEPARATOR = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
IMPORTING
FILELENGTH =
HEADER =
TABLES
 DATA_TAB = P_IT_PIR
EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17
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 P_IT_PIR IS INITIAL.
FG_DATA_EXIST = ''.
ENDIF.
ENDFORM. " F_GET_DATA
*& Form F_GENERATE_DATASET
 text
 -->P_V_FNAME text
 <--P_IT_PIR text
FORM F_GENERATE_DATASET USING P_V_FNAME LIKE FNAME
 CHANGING P_IT_PIR LIKE IT_PIR
 P_WA_PIR LIKE WA_PIR.
MESSAGE I001(ZHNC).
*OPENING FILE AT THE APPLICATION SERVER FOR WRITING
OPEN DATASET FNAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
IF SY-SUBRC EQ 0.
MESSAGE I002(ZHNC).
LOOP AT P_IT_PIR INTO P_WA_PIR.
SPLIT P_WA_PIR AT '*' INTO P_WA_PIR-LIFNR
 P_WA_PIR-MATNR
 P_WA_PIR-EKORG
 P_WA_PIR-WERKS
 P_WA_PIR-VERKF
 P_WA_PIR-TELF1
 P_WA_PIR-URZLA
 P_WA_PIR-REGIO
 P_WA_PIR-APLFZ
 P_WA_PIR-EKGRP
 P_WA_PIR-NORBM.
*TRANSFER THE FILE FROM INTERNAL TABLE TO APPLICATION SERVER
MESSAGE I003(ZHNC).
TRANSFER P_WA_PIR TO FNAME.
ENDLOOP.
*CLOSING THE FILE AT THE APPLICATION SERVER
CLOSE DATASET FNAME.
ENDIF.

Hello,
I made a similar program. You can have a look at it.
*& Form write_to_app_server
 text
--> p1 text
<-- p2 text
FORM write_to_app_server.
To get filename
PERFORM get_filename.
To write into the application server
OPEN DATASET g_filename_with_path FOR OUTPUT IN TEXT MODE.
IF sy-subrc = 0.
 LOOP AT <l_table> INTO <l_line>.
 TRANSFER <l_line> TO g_filename_with_path.
 ENDLOOP.
 CLOSE DATASET g_filename_with_path.
ELSE.
 CLOSE DATASET g_filename_with_path.
ENDIF.
To send mail
PERFORM send_mail.
ENDFORM. " write_to_app_server
*& Form get_filename
 text
--> p1 text
<-- p2 text
FORM get_filename.
DATA : l_log_path TYPE filepath-pathintern
 VALUE 'Y28M_DOWNLOADS_BACKGROUND' .
CALL FUNCTION 'FILE_GET_NAME_USING_PATH'
 EXPORTING
 client = sy-mandt
 logical_path = l_log_path
 operating_system = sy-opsys
 file_name = p_fname
 IMPORTING
 file_name_with_path = g_filename_with_path
 EXCEPTIONS
 path_not_found = 1
 missing_parameter = 2
 operating_system_not_found = 3
 file_system_not_found = 4
 OTHERS = 5.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. " get_filename
You may find it useful.
Regards,
Karuna.

How to start the file server for Agile PLM

Similar Messages

Maybe you are looking for