Migrate from wscp to wsadmin

The wscp tool was a part of the administration repository support in WebSphere Application Server Version 3.5. You can use the WebSphere Application Server - Express scripting client program, wsadmin, to do the same kinds of things wscp did, and more. You can use the JACL scripting language for scripts, but the elements specific to wsadmin are different from those available in wscp. This article shows how to create WebSphere Application Server - Express scripts that perform actions similar to those performed by wscp. Automatic conversion of scripts between the two releases is difficult.

Configuration commands for wscp

• create
• list
• modify
• remove
• show
• showall
• install
• uninstall
• all SecurityConfig commands
• all SecurityRoleAssignment commands
• clone
• removeClone

Other commands exist to provide ../admin/help for configuration commands. These commands include attributes, containment, and ../admin/help.

Operation commands for wscp

• start
• stop
• show (for runtime attributes)
• testConnection
• all DrAdmin commands
• regenPluginCfg

To convert wscp commands to wsadmin commands, follow these steps:

1. Find the corresponding configuration wsadmin WebSphere Application Server - Express object type for each configuration command. Use the AdminConfig create, list, modify, remove, show, and showAttribute commands to perform the same type of operations in WebSphere Application Server - Express that you performed in Version 3.5. Use this table to determine the corresponding types:

   wscp command	WebSphere Application Server - Express wsadmin configuration type
   ApplicationServer	Server
   Context	Not applicable
   DataSource	DataSource
   Domain	Not applicable
   EnterpriseApp	ApplicationDeployment
   GenericServer	Server
   J2CConnectionFactory	J2CConnectionFactory
   J2CResourceAdapter	J2CResourceAdapter
   JDBCDriver	JDBCProvider
   JMSConnectionFactory	JMSConnectionFactory
   JMSDestination	JMSDestination
   JMSProvider	JMSProvider
   MailSession	MailSession
   Module	ModuleDeployment
   Node	Node
   ServerGroup	ServerCluster
   URL	URL
   URLProvider	URLProvider
   VirtualHost	VirtualHost

2. Use the online help command of the AdminConfig object to determine the WebSphere Application Server - Express attribute names. For example: attributes, defaults, parents, required, or types. These examples illustrate the use of this command:

   • This example lists the attributes available for the Server object type:

     $AdminConfig attributes Server

   • This example lists the types you can configure:

     $AdminConfig types

   • This example lists the objects which contain the DataSource object type:

     $AdminConfig parents DataSource

3. Convert application installation commands:

   1. Run the installInteractive command on the AdminApp object from an interactive wsadmin session.
   2. Locate message WASX7278I in the wsadmin.traceout log file and use the data in the message to construct an installation command for your application.

4. Convert operational commands. Use this table to determine how to convert operational commands:

   wscp 3.5 action	wsadmin WebSphere Application Server - Express object and command	wsadmin WebSphere Application Server - Express MBean	wsadmin WebSphere Application Server - Express Operation
   server start	AdminControl startServer
   server stop	AdminControl stopServer
   application start	AdminControl invoke	ApplicationManager	startApplication
   application stop	AdminControl invoke	ApplicationManager	stopApplication
   check run-time attribute	AdminControl getAttribute	mbean	attribute
   check run-time attributes	AdminControl getAttributes	mbean	list of attributes
   regenPluginCfg	AdminControl invoke	PluginCfgGenerator	generate
   testConnection	AdminControl testConnection
   enable security	securityon command in securityProcs.jacl
   disable security	securityoff command in securityProcs.jacl

These help topics provide examples of migrating wscp commands to wsadmin commands. They are specific to migrating from WebSphere Application Server Version 4.0, but there are applicable to migrating from Version 3.5 also.

• Example: Migrating - Regenerating the node plug-in configuration
• Example: Migrating - Stopping an application server
• Example: Migrating - Modifying the virtual host
• Example: Migrating - Modifying and restarting an application server
• Example: Migrating - Pinging running servers for the current state
• Example: Migrating - Removing an application server
• Example: Migrating - Installing an application
• Example: Migrating - Installing a JDBC driver
• Example: Migrating - Testing the DataSource object connection
• Example: Migrating - Enabling security
• Example: Migrating - Disabling security