Create and Start the Default Service
You must create a default Application Dispatcher service to run any of
the sample programs supplied with SAS/IntrNet. Before you create the
service, you must reserve a TCP/IP port number for your default Application
Dispatcher service. Consult your system administrator or check your
services definition file to find an available port number.
You should create the default service with the SAS/IntrNet Configuration
Utility (inetcfg). This utility is available for
After you create and start the service, continue with
Adding the Default Service Definition
to the Broker configuration file.
Services can be created on Windows platforms with a configuration utility that is accessible from the Start menu.
Note: It is recommended that you install the SAS Service Configuration Utility before creating a SAS/IntrNet service if you ever intend to run the SAS server as a Windows service (except on Windows 95/98). Instructions for installing the SAS Service Configuration Utility may be found in an appendix of the SAS System Installation Instructions for Microsoft Windows.
Perform the following steps to create and start the default service:
- From the Start menu, select Programs
The SAS System (or other program group where the SAS System
is installed) IntrNet Create a New IntrNet Service.
The IntrNet Config Utility Welcome window appears.
- Read the information in the Welcome window, and then select
Next to continue. If you have not installed the SAS Service Configuration Utility (see note above), you will receive a Warning window. You can only continue creating the service if you do not intend to run this service as a Windows service. Otherwise, you should end the configuration utility, install the SAS Service Configuration Utility, and then create the default service.
- Select Create a Socket Service, then select Next
to continue.
- Type
default
as the name of the new service.
Select Next to continue.
- Specify the directory where you want the configuration utility to
place your service directory and control files. The default location
(under your SASUSER directory) is recommended. Select
Next to continue.
- Type the TCP/IP port number that you reserved for the default Application
Dispatcher service. Select Next to continue.
- A password is not necessary for the default service. You can add
an administrator password later if you use this service for production
applications. Select Next to continue.
- The Create Service window displays all of the information that you
specified for this service. Verify that the information is correct and then select
Next to create the service.
- Select Next and then Finish to complete the
setup of the default service.
- From the Start menu, select Programs
The SAS System (or other program group where the SAS System
is installed) IntrNet default Service Start Interactively. Your default Application
Server should now be running.
On UNIX platforms, the configuration utility is a Perl script. Perform
the following steps to create and start the default service:
- From a system prompt, submit the following command:
SASROOT/utilities/bin/inetcfg.pl
where SASROOT is the path to the SAS root directory.
As the configuration utility runs, you are prompted for information about
the service that you are creating.
- Press Return to accept the default value, which names the
service default.
- The next prompt asks for the name of the directory where all of
the service control files should be stored. Press Return to
accept the suggested value, or type the desired directory name and then
press Return.
- Type S and press Return to define a socket service.
- Press Return to select one server.
- Type the TCP/IP port number that you reserved for this service and
press Return.
- Press Return to skip entering an administrator password.
You can add an administrator password later if you use this service
for production applications.
- Verify the displayed information and press Return to create
the service. Note the path for the service directory.
- The configuration utility created a start.pl file to
start the default Application Server. Change to the service directory
path and start the server by submitting the following command:
./start.pl
The configuration utility provided for OS/390 is a batch job. It is
installed as a member named INETCFG in the CNTL data set that you created as
the first step in the installation of your SAS software. To use the utility,
you must edit the parameter file, member INETEDTP in the CNTL data set, edit
the INETCFG job, and then submit the INETCFG job. The INETEDTP member
contains the parameters necessary for creating a service.
To create and start the default service on OS/390, perform the following steps:
- Edit the member INETEDTP.
- Verify the name of the service that you are creating. The service name is
defined by the line beginning with ISVC= and
should be DEFAULT.
- Verify that the service is a socket service. The line containing
ISVCTYP=%SOCKETTYP should be uncommented.
- Locate the line I$-PORT1. Change the value 5001
to the correct port number or network service name for your Application
Server.
- Save and close INETEDTP.
- Edit INETCFG to verify the job header information. Verify that the
service name is DEFAULT. If you make changes, be sure to save
them. Do NOT change SASEDITP to INETEDTP because this is your original SAS
installation parameters file.
- Submit the INETCFG JCL job for processing. The INETCFG job will submit
another job (INETCFGA). Verify that both jobs completed with a return code
of 0. If they completed successfully, you now have the data sets and members
necessary for running the default service.
If the INETCFG job failed, examine the messages and sysprint members for
error messages. If you see a message that reads
ERROR: THIS REPLACEMENT CAUSES RESULT TO EXCEED OUTPUT LRECL
you might have supplied a pathname in one of your INETEDTP parameters that
is too long. Try shortening this pathname and rerun INETCFG.
Note: Before you run INETCFG again, you must delete any data sets
created by the previous failure of INETCFG. You can find these data sets by looking in
the namespace determined by your original SAS install. For example, if your
SAS software was installed with the prefix name SYS.SAS and your failed
INETCFG was trying to create the DEFAULT service, then delete
all data sets beginning with the name prefix SYS.SAS.WEB.DEFAULT
before running INETCFG again.
- The configuration utility creates a server root in a partitioned
data set (PDS) named prefix.WEB.DEFAULT, where prefix is the
data set prefix that you supplied during your SAS installation. The PDS contains
any JCL procedures and server start-up code required for starting the service.
You will find the following members:
- APSTRT1
- contains the JCL necessary to run the corresponding @APSTX1 file
as a started task. You should move this file to your started task
library and enable it as a started task.
- @APSTX1
- contains the SAS code that invokes the server. This file is called by
the JCL in the corresponding APSTRT1 file. This SAS program must
remain in the PDS where it was created.
In addition to the server root PDS, the configuration utility creates an
empty PDS named prefix.WEB.DEFAULT.TDIR, where prefix is the
data set prefix that you supplied during your SAS installation. The Application
Server will use this PDS as a scratch location.
- You must modify the permissions for the data sets created above so that
the server can write to them as necessary. To modify the permissions, create
a special RACF data set profile that applies to all the data sets in this
service (prefix.WEB.DEFAULT.*). The RACF data set profile should also
grant write access to the userid of the Application Server.
- Issue a START command from the system console to start the default
Application Server.
To create and start the default service on OpenVMS, perform the following steps:
- From a system prompt, submit
@sas$root:[tools]inetcfg.com
.
As the configuration utility runs, you are prompted for information
about the service that you are creating.
- Press Return to name the service DEFAULT.
- Press Return to accept the suggested value for the server root
directory.
- Type S to define a socket service.
Press Return to continue.
- Press Return to select one server for this service.
- Type the TCP/IP port number or name that you reserved for the default
Application Server and press Return.
- A password is not necessary for the default service. You can add an
administrator password later if you use this service for production
applications. Press Return to continue.
- The utility displays the information that you entered for this service. Verify
that the information is correct. If the information is correct, press
Return to create the service. Read the messages to determine if the
service was created correctly. One of these messages contains the path for
the service directory created by the utility. You should note this path for
use later in this process.
- The configuration utility created a START.COM file that starts the
default Application Server. To start the server, change to the service
directory created by the utility. Then submit the following command:
@START.COM
To create and start the default service on CMS, perform the following steps:
- From the ready prompt, execute the INETCFG EXEC:
inetcfg
As the configuration exec runs, you are prompted for information
about the service that you are creating. At any prompt, you can enter
quit
or exit
to terminate the exec.
At each prompt, the default response is displayed in parentheses; you can
choose that response by pressing Enter.
- At the first prompt, type
default
as the name of the service.
- The next prompt is for the type of service that you are defining. Press
Enter to accept the default Socket type, because the other types are
not supported on CMS.
- Press Enter to select one server for this service.
- Type the TCP/IP port number or name that you reserved for the default
Application Server.
- A password is not necessary for the default service. You can add an
administrator password later if you use this service for production
applications. Press Enter to continue.
- The INETCFG EXEC displays the information that you have entered so far. Verify
that the information is correct and press
Yes
to accept it or
No
to exit.
- INETCFG EXEC asks for a location where you want the configuration
files to be written. Specify either a filemode letter or an SFS directory
name that you have write access to.
- INETCFG EXEC asks for the location where the sample source files will
be accessible to the server at the time that it is running. Specify either
a filemode letter that the server will have accessed, a minidisk userid and
address that the server will be able to link to, or an SFS directory name
that the server will have read authority for.
- INETCFG EXEC asks for the location where the sample data
will be accessible to the server at the time that it is running. Specify
either a filemode letter that the server will have accessed,
a minidisk userid and address that the server will be able to link to, or
an SFS directory name that the server will have read authority for.
- INETCFG EXEC completes by creating a SAS program and a start-up EXEC for the
server, and displays the list of steps you need to take to complete the
installation.
If you have created the configuration files in a staging area,
you will need to move them to the respective servers' disks.
To have a server automatically start when it is logged on,
use the generated exec as its PROFILE EXEC,
or include the code from the exec in an existing
PROFILE EXEC.
- Execute the start-up EXEC to start the default Application Server.