Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

IBM Exam C9510-401 Topic 7 Question 90 Discussion

Actual exam question for IBM's C9510-401 exam
Question #: 90
Topic #: 7
[All C9510-401 Questions]

A system administrator has created a Jython script called globalScript.py.

What should the administrator do to ensure globalScript.py is loaded when the wsadmin shell is used?

Show Suggested Answer Hide Answer
Suggested Answer: C

Process embedded configuration

Specifies whether the embedded configuration should be processed. An embedded configuration consists of files such as resource.xml, variables.xml, and deployment.xml. You can collect WebSphere Application Server-specific deployment information and store it in the application EAR file. Such an EAR file can then be installed into a WebSphere Application Server configuration, using application management interfaces that are described in the topic, Installing an application through programming.

One such application EAR file is an enhanced EAR file, which is created when you export an already installed application. The embedded configuration check box identifies such an enhanced EAR file. By default, the check box for 'process embedded configuration' is checked if the application is detected to be an enhanced EAR. The application install options are prepopulated with the information from the embedded configuration whether the check box for 'process embedded configuration' is checked or not. Users can overwrite these values during the deployment process.

References: https://www.ibm.com/support/knowledgecenter/SSAW57_8.0.0/com.ibm.websphere.nd.doc/info/ae/ae/urun_rapp_installoptions.html


Contribute your Thoughts:

Rashida
26 days ago
Wait, there's a 'wsadmin' shell? I thought we were all about the 'bash' these days. Maybe the admin is stuck in the past, like my grandpa and his IBM mainframe.
upvoted 0 times
Tawna
5 days ago
C: Really? I didn't know about the wsadmin shell either.
upvoted 0 times
...
Jarvis
6 days ago
B: D) Set the script profiles in the wsadmin.properties file to load globalScript.py.
upvoted 0 times
...
Laurel
7 days ago
A: A) Compile globalScript.py to a Java class in the bin directory.
upvoted 0 times
...
...
Elin
1 months ago
I bet the admin's trying to make this script available to everyone, not just themselves. Option D is the way to go for that.
upvoted 0 times
...
Angelo
1 months ago
Modifying the configureCustomProperty script? That doesn't sound like the right approach. I think the wsadmin.properties file is the way to go.
upvoted 0 times
Tegan
9 days ago
A: Compile globalScript.py to a Java class in the bin directory.
upvoted 0 times
...
...
Carmen
1 months ago
I'm not sure why the administrator would need to compile the script to a Java class. That seems like overkill.
upvoted 0 times
...
Avery
1 months ago
Option D is the correct answer. It's the easiest way to ensure the script is loaded every time the wsadmin shell is used.
upvoted 0 times
Anglea
9 days ago
Yes, it's a convenient way to ensure the script is always available.
upvoted 0 times
...
Truman
25 days ago
That makes sense, it's a simple solution.
upvoted 0 times
...
Melda
1 months ago
D) Set the script profiles in the wsadmin.properties file to load globalScript.py.
upvoted 0 times
...
...
Sherrell
2 months ago
Interesting point, King. I can see how that could work as well. It's important to consider all options before making a decision.
upvoted 0 times
...
King
2 months ago
I disagree, I believe the correct answer is A. Compiling globalScript.py to a Java class in the bin directory seems like the right approach.
upvoted 0 times
...
Sherrell
2 months ago
I think the answer is D, because setting the script profiles in the wsadmin.properties file would ensure globalScript.py is loaded.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77