96 lines
6.5 KiB
HTML
96 lines
6.5 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
<!DOCTYPE html
|
||
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
<html lang="en-us" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow" />
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<meta name="DC.Type" content="task" />
|
||
|
<meta name="DC.Title" content="Create an application definition" />
|
||
|
<meta name="abstract" content="Review this topic to learn how about the two different types of applications that you can define and work with." />
|
||
|
<meta name="description" content="Review this topic to learn how about the two different types of applications that you can define and work with." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahurzahu444worksecureapps.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahuappdefconcept.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="define_app" />
|
||
|
<meta name="DC.Language" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
<title>Create an application definition</title>
|
||
|
</head>
|
||
|
<body id="define_app"><a name="define_app"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Create an application definition</h1>
|
||
|
<div><p>Review this topic to learn how about the two different
|
||
|
types of applications that you can define and work with.</p>
|
||
|
<div class="section"> <p>There are two types of application definitions that you can work
|
||
|
with in DCM: application definitions for server or client applications that
|
||
|
use SSL and application definitions that you use for signing objects. </p>
|
||
|
<p>To
|
||
|
use DCM to work with SSL application definitions and their certificates, the
|
||
|
application must first be registered with DCM as an application definition
|
||
|
so that it has a unique application ID. Application developers register SSL-enabled
|
||
|
applications by using an API (<a href="../apis/qsyrgap.htm">QSYRGAP, QsyRegisterAppForCertUse</a>) to create the application
|
||
|
ID in DCM automatically. All IBM<sup>®</sup> <span class="keyword">iSeries™</span> SSL-enabled
|
||
|
applications are registered with DCM so that you can easily use DCM to assign
|
||
|
a certificate to them so that they can establish an SSL session. Also, for
|
||
|
applications that you write or purchase, you can define an application definition
|
||
|
and create the application ID for it within DCM itself. You must be working
|
||
|
in the *SYSTEM certificate store to create an SSL application definition for
|
||
|
either a client application or a server application.</p>
|
||
|
<p>To use a certificate
|
||
|
to sign objects, you first must define an application for the certificate
|
||
|
to use. Unlike an SSL application definition, an object signing application
|
||
|
does not describe an actual application. Instead, the application definition
|
||
|
that you create might describe the type or group of objects that you intend
|
||
|
to sign. You must be working in the *OBJECTSIGNING certificate store to create
|
||
|
an object signing application definition.</p>
|
||
|
<p>To create an application definition,
|
||
|
follow these steps: </p>
|
||
|
</div>
|
||
|
<ol><li class="stepexpand"><span><a href="rzahurzahu66adcmstart.htm#rzahu66a-dcm_start">Start
|
||
|
DCM</a>. </span></li>
|
||
|
<li class="stepexpand"><span>Click <span class="uicontrol">Select a Certificate Store</span> and select
|
||
|
the appropriate certificate store. (This is either the *SYSTEM certificate
|
||
|
store or the *OBJECTSIGNING certificate store depending on the type of application
|
||
|
definition that you are creating.)</span> <div class="note"><span class="notetitle">Note:</span> If you have questions
|
||
|
about how to complete a specific form in this guided task, select the question
|
||
|
mark (<span class="uicontrol">?</span>) at the top of the page to access the online
|
||
|
help. </div>
|
||
|
</li>
|
||
|
<li class="stepexpand"><span>When the Certificate Store and Password page displays, provide
|
||
|
the password that you specified for the certificate store when you created
|
||
|
it and click <span class="uicontrol">Continue</span>.</span></li>
|
||
|
<li class="stepexpand"><span>In the navigation frame, select <span class="uicontrol">Manage Applications</span> to
|
||
|
display a list of tasks.</span></li>
|
||
|
<li class="stepexpand"><span>Select <span class="uicontrol">Add application</span> from the task list
|
||
|
to display a form for defining the application.</span> <div class="note"><span class="notetitle">Note:</span> If you are
|
||
|
working in the *SYSTEM certificate store, DCM will prompt you to choose whether
|
||
|
to add a server application definition or a client application definition. </div>
|
||
|
</li>
|
||
|
<li class="stepexpand"><span>Complete the form and click <span class="uicontrol">Add</span>. The information
|
||
|
that you can specify for the application definition varies based on the type
|
||
|
of application that you are defining. If you are defining a server application,
|
||
|
you can also specify whether the application can use certificates for client
|
||
|
authentication and must require client authentication. You can also specify
|
||
|
that the application must use a CA trust list to authenticate certificates. </span></li>
|
||
|
</ol>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahurzahu444worksecureapps.htm" title="This topic provides information about creating application definitions and how to manage an application's certificate assignment. You can learn about defining CA trust lists that applications use as the basis of accepting certificates for client authentication.">Manage applications in DCM</a></div>
|
||
|
</div>
|
||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="rzahuappdefconcept.htm" title="Use this information to learn what DCM application definitions are and how to work with them for SSL configuration and object signing.">Application definitions</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|