INTRODUCTION TO NET
APPLICATION DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
The log file Indicated on the Diagnostics page of the WebLogic Server administration console
|
|
|
The system logs of the compute node that hosts the WebLogic administration serve
|
|
|
The Activity page of the service web console
|
|
|
The WebLogic Service logs extracted using the Java Cloud Service REST API
|
Detailed explanation-1: -By default, the server log file is located in the logs directory below the server instance root directory; for example, DOMAIN NAME servers NAME logs NAME. log, where DOMAIN NAME is the name of the directory in which you located the domain and SERVER NAME is the name of the server.
Detailed explanation-2: -A WebLogic Server instance maintains a server log (the SERVER NAME. log file in the DOMAIN NAMENAMEdirectory), where it records all messages from each of the subsystems as well all the applications deployed on that server.
Detailed explanation-3: -If you create the domain in development mode, the wizard saves the username and encrypted password in a boot identity file. A WebLogic Server instance can refer to a boot identity file during its startup process. If a server instance does not find such a file, it prompts you to enter credentials.
Detailed explanation-4: -Log in by using the administrative credentials (user name and password) that you used when you created the WebLogic domain. In the Domain Structure menu, click Deployments and then click Install in the Deployments section. In the Install Application Assistant, specify the name of the application archive file for Path.
Detailed explanation-5: -WebLogic logging services provide facilities for writing, viewing, filtering, and listening for log messages. These log messages are generated by WebLogic Server instances, subsystems, and Java EE applications that run on WebLogic Server or in client JVMs.
Detailed explanation-6: -Login to the Admin Console using your weblogic account. Navigate to the correct page: DOMAIN > Environment > Servers > ServerName (msD2-01 for me) > Debug. Click on the ‘Lock & Edit’ button. Expand the scope ‘weblogic’ and then ‘security’ More items •25-Nov-2017