Difference between revisions of "App Server Operations"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 3: | Line 3: | ||
{{:Restart the Application Server}} | {{:Restart the Application Server}} | ||
{{:Stop the Application Server}} | {{:Stop the Application Server}} | ||
{{:Accessing the Application Server}} | {{:Accessing the Application Server}} | ||
{{:Creating a Tenant}} | {{:Creating a Tenant}} |
Latest revision as of 22:53, 28 September 2015
Server Restart Sequence
When an installation employs memcached or the Messaging Server, it is important to follow this sequence when restarting servers:
# STOP THE MESSAGING SERVER, if one is running: /etc/init.d/messaging stop {hornetq-folder}/bin/stop.sh # STOP ALL APPLICATION SERVERS # On each server: {install-dir}/profiles/IS_default/bin/shutdown.sh # STOP ALL memcached SERVERS # On each server: /bin/memcached -d stop # START ALL memcached SERVERS # On each server: /bin/memcached -d start -p {port} -u {user} -m {MB_of_memory} # Typical values: # Port: 11211, User: root, MB of memory: 25 # START ALL APPLICATION SERVERS # On each server: {install-dir}/profiles/IS_default/bin/startup.sh # START THE MESSAGING SERVER, if you're running one: {hornetq-folder}/bin/start.sh /etc/init.d/messaging start
- Considerations
-
- Stopping application servers ensures that they aren't adding entries to the cache.
- Stopping memcached makes sure that the cache is flushed.
- Those two steps can occur in either order. It is the next two for which order is critical:
- Restarting memcached first makes sure that a clean copy of the cache is available.
- When the application servers come up, they use the clean cache.
Start the Application Server
- Login as root
- {install-dir}/profiles/IS_default/bin/startup.sh
Restart the Application Server
- Login as root
- {install-dir}/profiles/IS_default/bin/restart.sh
Stop the Application Server
To stop the application server, you kill the Apache Tomcat container it's running in.
- Login in as root
- {install-dir}/profiles/IS_default/bin/shutdown.sh
Accessing the Application Server
After the application server has been started:
- 1. Access the Service Provider URL: http://{yourDomain}/networking/Service?t=1&targetpage=ViewPort.jsp:
- Where:
- {yourDomain} is the platform domain. For example: yourcompany.com
- Default username and password: Use the credentials you typed into the Software AG installer.
- The platform will request that you change your password after you login the first time.
- 2. Setup the Service Configuration with these required parameters:
- Configure the Service Settings and specify Service and Domain names:
Parameter Description Typical Value Service Name Name of the service provider Financiocorp Services Prefix for Service Domain Optional subdomain name Allowed characters: a-z, A-Z, 0-9, - (alphanumeric, plus hyphen)
Example: service
Service Domain The Domain Name part of the URL mydomain.com Domain URL Read Only
Automatically populated as:- Prefix + Service Domain
service.mydomain.com
Creating a Tenant
- After Login, create a new tenant from a web browser using the URL as follows:
- https://yourdomain.com/networking/Service?t=2308
- Where yourdomain.com is the name of your domain