Skip to main content

Working with Linux MID Servers

some useful UNIX commands

e.g. via Putty

downloading the agent folder for a manual MID server upgrade:
use curl url

MID Server Stop/Start/Status commands

stop the MID server:
using command
sudo /usr/bin/systemctl stop mid

start the MID server:
using command
sudo /usr/bin/systemctl start mid

status of MID:
/usr/bin/systemctl status mid

rename the agent folder to old_agent using:
mv agent old_agent_nov2019

delete operations
delete folder and contents:
rm -rf <folder_name>
delete file:
rm <file_name>

restore backup files
navigate to the folder
run commands to restore backup files:
cp config.xml /app/midserver/agent/
cp wrapper-override.conf /app/midserver/agent/conf/
cp agent_keystore.jks /app/midserver/agent/keystore/
cp cacerts /app/midserver/agent/jre/lib/security/

list directory contents
use 
ll

exit back to prompt
ctrl c

view a file contents read only
vi /app/midserver/agent/conf/wrapper-override.conf
then  :q to exit without saving

pull down a log file
2019-08-05 08:34:49 PROD root@<user>:~> $ find / -name *glide-dist-upgrade.log* 2>>/dev/null 

search for something
ps -ef | grep -i "upgrade"

check port 443
netstat -ano | grep 443

display current directory
pwd

create a directory, e.g. 'keystore' in agent folder

mkdir keystore

grant permissions on a folder
You can use command : chmod 777

Comments

Post a Comment

Popular posts from this blog

ServiceNow timeout settings for virtual agent chat

  After connecting to live agent User is connected to live agent and not responding to live agent chat or distracted. The below properties controls the timeout settings, the OOB settings for reminder is [180 sec] and for cancelling the chat is [360 sec]. The job is default configured to 2 min so I believe no tweaking is required here.  Property -   com.glide.cs.idle_chat_reminder_timeout                  com.glide.cs.idle_chat_cancel_timeout Scheduled job   - Idle Chat Timer Task   https://community.servicenow.com/community?id=community_article&sys_id=1453b03bdbaad0109e691ea668961929   (ServiceNow ) 
Post a Comment
Read more

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){...
Post a Comment
Read more