Use sccinstance.bat (Windows) or sccinstance (UNIX) to deploy an instance of SAP Control Center from a shared-disk installation or to manage existing instances.
You can run multiple instances of SAP Control Center, including SCC servers, SCC agents, or a mixture of the two, from a single installation on a shared disk.
sccinstance[.bat] [-agent] [-c | -create] [-d | -debug] [-disable] [-enable] [-f | -force] [-h | -help] [-host host-name] [-i | -instance [instance-name]] [-l | -list] [-plugins {plugin-ID,plugin-ID,...}] [-portconfig {port-name=port-number,port-name=port-number, ...}] [-refresh] [-r | -remove] [-s | -server] [-service] [-silent]
sccinstance assumes that the host name is the same as the instance name unless you use -host to specify a different host name.
Port information:
Port Name | Description | Service Names | Property Names | Default Port |
---|---|---|---|---|
db | Database port Present on SCC server |
SccSADataserver Messaging Alert Scheduler |
com.sybase.asa.server.port messaging.db.port alert.database.port org.quartz.dataSource.ASA.URL |
3638 |
http | Web HTTP port Present on SCC server |
EmbeddedWebContainer | http.port | 8282 |
https | Web HTTPS (secure HTTP) port Present on SCC server |
EmbeddedWebContainer | https.port | 8283 |
jiniHttp |
JINI HTTP server Present on SCC server and SCC agent |
Jini | httpPort | 9092 |
jiniRmid |
JINI remote method invocation daemon Present on SCC server and SCC agent |
Jini | rmidPort | 9095 |
msg | Messaging port Present on SCC server |
Messaging | messaging.port | 2000 |
rmi | RMI port Present on SCC server and SCC agent |
RMI | port | 9999 |
tds | Tabular Data Stream™ port (used to communicate with other SAP database products) Present on SCC server and SCC agent |
Tds | tdsPort | 9998 |
You can also use -refresh to convert a server to an agent or an agent to a server (see the examples). Files are removed or added to change the function of the instance. Use alone or with -agent to refresh an agent instance, or with -server to refresh a server instance. Generates an error if the instance is running.
sccinstance -enable sccinstance -create -server -instance Boston -service net start "SAP Control Center 3.3 (Boston)"
sccinstance -create -agent -serviceor
sccinstance -create -service
sccinstance -create -server -portconfig rmi=8888,http=7070,https=7071
sccinstance -create -agent -instance fireball -portconfig rmi=9991 sccinstance -create -agent -instance fireball2 -host fireball -portconfig rmi=9992
sccinstance -refresh -server
sccinstance -refresh -agent -instance kalamazoo
sccinstance -remove -instance porcupine
sccinstance
sccinstance -list
$ sccinstance -list 2 SCC instances deployed: SCC instance node1 deployed in agent mode for host node1 RMI port 9999 SCC instance node2 deployed in agent mode for host node2 RMI port 9999
Both instances use the same RMI port. You must either reassign ports for one instance or remove it. But you get an error if you try remove an instance when another instance is running on the same host:
$ sccinstance -instance node2 -remove [ERROR] Command execution failed. [ERROR] SCC instance node2 could not be removed because it is running. Shut down the SCC before removing the instance.
Use the -force option to override the error and force the removal of the second agent instance:
$ sccinstance -instance node2 -remove -force Removing SCC instance node2 ... SCC instance node2 was successfully removed.
sccinstance permission defaults to all users, except as noted for certain parameters.