Versions Compared

Old Version 6

changes.mady.by.user Kim Rasmussen

Saved on

compared with

New Version 7

changes.mady.by.user Kim Rasmussen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The developer portal is started using a Ceptor launcher. In the default installation it comes with its own launcher file config/ceptor_launch_developerportal.xml which can either be used to start up the developer portal by it self on its own server or the launch configuration can be copied into the in config/ceptor_launch.xml and it can be started  can be used so the developer portal starts with the rest of Ceptor.

The standard launcher that comes with the Ceptor distribution is as such:

Code Block
languagexml
titleppceptor_launch_developerportal.xml
linenumberstrue
<?xml version="1.0" encoding="UTF-8"?>
<!-- PortalProtectCeptor Launcher configuration -->
<portalprotectlauncher port="28211"
	launcherclasspath="classes/launcher;lib/PortalProtectAgent.jar;extlib/logback-core-1.2.1.jar;extlib/logback-classic-1.2.1.jar;extlib/slf4j-api-1.7.24.jar" jvmstartdelay="5">
	<!-- Ceptor API developer portal -->
	<jvm name="apideveloperportal" vmargs="-Xmx1024M -Xnoclassgc -XX:+HeapDumpOnOutOfMemoryError -XX:+ExitOnOutOfMemoryError">
        <config servers="nios://localhost:21233?validateservercert=false" />
        <classloader name="con" extraclasspath="">
            <service name="apideveloperportal" launcherclass="io.ceptor.apimanager.developerportal.DeveloperPortalLauncher">
                <property name="sessioncookiename" value="jsession_ceptordeveloperportal"/>
                <webserver webapp="${portalprotect.home}/ppserver/developerportal"
                    contextpath="/"
                    bindaddress="0.0.0.0" httpport="4848" sslport="4843" minthreads="2" maxthreads="32"
                    maxpostsize="67108864" maxidletime="10000"
                    responseheadersize="32768"
                    outputbuffersize="32768" keystoretype="JKS"
					keystore="${portalprotect.home}/ppserver/portalprotect.key"
					password="changeit" 
                    />
            </service>
        </classloader>
	</jvm>
</portalprotectlauncher>

...

As written above it can be merged with other launchers or started as stand alone. This is up to the individual environment setup and deployment.

Note

The default ceptor_launch.xml launcher configuration file starts the API Developer Portal on the context path /apideveloperportal - this matches the default Ceptor Gateway configuration, which forwards all calls to /apideveloperportal to the API Developer Portal server running on port 4843.


Configuration

The developer portal requires only a few lines of configuration in the ceptor-configuration.xml in order to start up. The standard distribution comes pre-configured and can be changes as needed.

...