0% found this document useful (0 votes)
35 views

Setting Up WAS Process

To create a WAS profile using the Profiles Management tool: 1. Start the tool from the bin directory 2. Choose application server and then typical profile creation 3. Click create to generate the profile

Uploaded by

tmallikarjunar
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
35 views

Setting Up WAS Process

To create a WAS profile using the Profiles Management tool: 1. Start the tool from the bin directory 2. Choose application server and then typical profile creation 3. Click create to generate the profile

Uploaded by

tmallikarjunar
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Creating a WAS Profile:

To create a profile, complete the following steps: 1. Start the Profiles Management tool by opening a command prompt and changing to the following directory:

o o
2.

Linux:
opt/IBM/WebSphere/AppServer/bin/ProfileManagement

Windows:
C:\IBM\WebSphere\AppServer\bin\ProfileManagement

Type the following command to start the tool:


pmt

3. 4. 5.

When asked to choose an environment, select Application server, and then click Next. Choose Typical profile creation, and then click Next. Make sure that Enable administrative security check box is not selected. You will configure security when you complete the procedure described in the topic, Setting up federated repositories.

Click Create to create the profile. single profile in WebSphere Application Server, you can do so using a JACL script.

To create WebSphere Application Server process, complete the following steps: 1. Create a JACL file named createConnectionsServer.jacl and include the commands that create server processes for each feature you want to include in the profile. See the information provided in the WebSphere Application Server information center for more details. http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.doc/info/ aes/ae/txml_createserver.html The following sample JACL file creates a server process for each of the Lotus Connections features.
### ### *** PLEASE READ THIS IMPORTANT NOTE REGARDING FOLLOWING CODE ***

2. 3. 4. 5. 6.

### In lines of code below, the characters \r identify a carriage return. 7. ### These visual carriage returns were added to this document to prevent 8. ### long lines of text from running off the printed page. 9. ### 10. ### DO NOT not include the \r in your file; instead, remove it and 11. ### add the line it identifies as a broken line to your file as a single 12. ### line. 13. 14. 15. 16. ### Create a server using the supplied server name and node 17. 18. ### createConnectionsServer.jacl 19. ###

20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60.

### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###

Create the servers for Lotus Connections About: This script uses the given node and server arguments to create Lotus Connections servers on a Webphere Application Server. Usage: wsadmin.sh -username system \ -password password \ -f /createConnectionsServer.jacl server Parameters: arg1 - server to create Servers: Activities - ActivitiesServer Blogs - BlogServer Communities - CommunitiesServer Dogear - DogearServer Profiles - ProfilesServer

proc createserver {serverArg} { ### ### Globals ### global AdminConfig global AdminControl global AdminApp set node [$AdminConfig list Node] set nodeName [$AdminConfig showAttribute $node name] ### ### Is a server by this name already running on the node? ###

puts "createConnectionsServer: Checking to see if server $serverArg is \r 61. already running on node $nodeName" 62. set runningServer [$AdminControl completeObjectName \r 63. type=Server,node=$nodeName,process=$serverArg,*] 64. if {[llength $runningServer] > 0} { 65. puts "createConnectionsServer: Error -- Server $serverArg \r 66. already running on node $nodeName" 67. puts "createConnectionsServer: Error -- exiting script" 68. return 69. } 70. 71. 72. puts "createConnectionsServer: Creating the server $serverArg on \r 73. node $nodeName..." 74. set name_attribute [list name $serverArg] 75. set attributes [list $name_attribute] 76. set server [$AdminConfig create Server $node $attributes] 77. 78. ### 79. ### Save the change

80. 81. 82. 83. 84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95.

### puts "createConnectionsServer: Saving the configuration" $AdminConfig save } ### ### Main ### puts "createConnectionsServer: Starting - Lotus Connections server creation"

if { !($argc == 1) } { puts "createConnectionsServer: This script requires a parameter: \r 96. the server to create" 97. puts "e.g.: createConnectionsServer.jacl ActivitiesServer" 98. puts " createConnectionsServer.jacl BlogsServer" 99. puts " createConnectionsServer.jacl CommunitiesServer" 100. puts " createConnectionsServer.jacl DogearServer" 101. puts " createConnectionsServer.jacl ProfilesServer" 102. } else { 103. set serverArg [lindex $argv 0] 104. 105. createserver $serverArg 106. } 107. puts "createConnectionsServer: Finished - Lotus Connections server creation"

108. Copy the createConnectionsServer.jacl file you created into the bin subdirectory of the profile. For example:

o o

Linux:
opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

Microsoft Windows:
C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin

109. Start the WebSphere Application Server profile to which you want to add the server processes. For example:
startServer server1

110.

Run the JACL file by typing the following command:

o o o o o o o

Linux:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin> ./wsadmin.sh -username <username> -password <password> -f createConnectionsServer.jacl <servername>

Microsoft Windows:
C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\wsadmin.bat -username <username> -password <password> -f createConnectionsServer.jacl <servername>

You might also like