Setting up SCAUTO server

[garlit]

Hi There,

I've upgraded our SC RTE on Unix Solaris (Dev) from 3.0 to 5.1. I've just upgraded SCAUTO also however I'm not having much luck getting the SCAuto Server started.

In the sc.ini file I have an entry
scauto:scdp

scdp being the service specified in the /etc/services file.

In the scstart script for 3.0 we used to have a command line that began ..

scautod -log.......&

This command does not appear to be valid anymore and in fact looking in the RUN directory there is no such executable.

Are you supposed to start up the SCAUTO server using
"scenter listener" and how does it show up in the status panel in ServiceCenter once it is up and running? Is it still Auto Server or is it listener?

Any help would be much appreciated.

Thanks
Jane

[fjespersen]

If you are using SC 5.1.2 you could have the following license problem:

S Y M P T O M

Attempting to connect an external interface product to ServiceCenter using SCAUTO does not work. The ServiceCenter and external product log files will indicate a license error even though the customer is licensed for the product. Note that the scenter -reportlic will indicate the the license is correct.

C A U S E

The license code and corresponding evaluation code within the Run Time Environment (RTE) do not correctly evaluate the license rights. The issue has been assessed and SCR 30332 been opened by Product Development to address the issue.

W O R K A R O U N D / F I X

Customer Support has been made aware of the issue and are prepared to respond. Open a ticket with Customer Support requesting a temporary authorization code with all scautomate products enabled. You can do so either by contacting Customer Support by phone or email, or open a ticked using the Customer Support web site.

Copied from support document: SA6-C0T-VWW1

[fid509]

Patch 4 has been released for SC 5.1.2. This should solve this kind of problem.
Furthermore, scautod has been replaced by the scenter executable. The scstart script has been modified so the startup of SCAutod is corrected. This is the cas with AIX so I think it is valid too on other platforms.

[fid509]

From the Peregrine Support Site

Q U E S T I O N or T O P I C

How are SCAUTOD and SCDBUTIL started in ServiceCenter 5.1? It does not appear that the SCAUTOD executable is provided in 5.1.


A N S W E R or C O N T E N T

SCAUTOD
Versions Prior to ServiceCenter 5.1
ServiceCenter releases prior to ServiceCenter 5.1 have an executable in the RUN directory called scautod.exe on Windows or scautod.rdbms on UNIX. This executable is used to start the listening process through which the SCAuto adapters communicate. This process listens on the port specified by the scauto parameter.

ServiceCenter 5.1
The scautod executable has been eliminated in ServiceCenter 5.1. In ServiceCenter 5.1 the standard scenter executable is used as the listener process for SCAuto adapters. Thus executing scenter -listener:scautoport in 5.1 is equivalent to executing scautod -scauto:scautoport in older releases.

Running ServiceCenter on Windows - How does this change effect operations?
This change should be transparent on Windows. If scautod is present in the sc.cfg file, the ServiceCenter service will automatically replace the scautod with scenter and start the scenter listener on the port specified by the scauto parameter.
Note: Replacement of the scautod in the sc.cfg file with scenter -listener:scautoport is recommended to avoid confusion but the change is not required for successful operations.

Running ServiceCenter on UNIX - . How does this change effect operations?
The scstart script distributed with ServiceCenter 5.1 has been modified such that it will start a scenter process instead of an scautod process. The scenter process will listen on port 12690, the default port for SCAuto.
Note: If port 12690 is not used, modification of the scstart script to use the appropriate port will be required. If a customized scstart script is being used and the scstart script distributed with ServiceCenter 5.1 is not being used, edit the customized script to replace the scautod with scenter and specify the correct listener port. An example of the change required to the ServiceCenter 5.0 scstart is as follows:

echo "Starting SCAutomate server..."
scautod -log:${LOGDIR}/scautod.log > ${LOGDIR}/autod.log 2>&1 &
sleep 1

requires editing to be similar to the following:

echo "Starting SCAutomate server..."
scenter -listener:12690 -log:${LOGDIR}/scautod.log > ${LOGDIR}/autod.log 2>&1 &
sleep 1

SCAuto is started internally (start scheduler in Status) - How does this change effect operations?
The ServiceCenter 5.1 RTE will automatically replace scautod in the start-up record with scenter and use the port number in the scauto parameter to start the correct scenter -listener:scautoport. As such, no changes are required.

SCDBUTIL
Starting with ServiceCenter version 5.1, the SCDBUTIL utility is started by running the following command:

scenter -util

Although the scdbutil executable still exists, scenter -util is the preferred method to start the utilities

[garlit]

Thanks, this is exactly what I was looking for. Have got it all working correctly now.