Running the JWSNAME Web Service From WebLogic Workshop
C-18
BEA Systems, Inc.
System.out.println("<<<< end: "+ cal_end.getTimeInMillis());
Display the end time of execution to the WEBLOGIC CONSOLE
diff=cal_end.getTimeInMillis()-cal_start.getTimeInMillis();
//Calculating the difference (execution time)
System.out.println("<<<< EXECUTION time in Milliseconds:" +diff);
//Displaying the execution time to the WEBLOGIC Console
//writing to file
out.write( "start time: "+ cal_start.getTimeInMillis()+"\n");
out.write("end time: "+cal_end.getTimeInMillis()+"\n");
out.write("execution time : "+diff+"\n");
out.close(); //closing file
}
}
The results of the execution are saved in a file as follows:
start time: 1073598362655
end time: 1073598362775
execution time : 120
Running the JWSNAME Web Service for an RFC
The following procedure describes how to run the JWSNAME for a Remote Function Call
(RFC). You first must ensure that WebLogic Server is running. For more information on
confirming that WebLogic Server is running, see
Confirming WebLogic Server is Running
and
How to Start WebLogic Server
.
Summary of Contents for WebLogic Server
Page 1: ...BEA WebLogic Adapter for SAP User s Guide DN3501342 0406 April 19 2006 ...
Page 8: ...viii BEA Systems Inc ...
Page 22: ...Component Information for the BEA WebLogic Adapter for SAP 1 10 BEA Systems Inc ...
Page 54: ...Creating an XML Schema 3 20 BEA Systems Inc ...
Page 163: ...Management and Monitoring BEA WebLogic Adapter for SAP User s Guide 7 45 ...
Page 164: ...7 46 BEA Systems Inc ...
Page 294: ...Using Staging BAPIs to Retrieve SAP BW Metadata D 14 BEA Systems Inc ...