DataTables Server-side processing (5,000,000 rows)

DataTables Server-side processing (5,000,000 rows)

DataTables erver-side processing (5,000,000 rows)

DataTables’ server-side processing mode is a feature that naturally fits with Scroller. Server-side processing can be used to show large data sets, with the server being used to do the data processing, and Scroller optimising the display of the data in a scrolling viewport.

When using server-side processing, Scroller will wait a small amount of time to allow the scrolling to finish before requesting more data from the server (200mS by default). This prevents you from DoSing your own server!

This example shows Scroller using server-side processing mode and 5 million rows. Important This particular example uses ajax as a function to fake the data to show Scroller’s ability to show large data sets. It does not have a real database behind it! You would normally not use ajax as a function to generate data, but rather as a url for where to fetch the real data!

In this example we also enable the scroller.loadingIndicator option of Scroller to show the end user what is happening when they scroll passed the currently loaded data.

ID First name Last name ZIP / Post code Country
138-1 138-2 138-3 138-4 138-5
139-1 139-2 139-3 139-4 139-5
140-1 140-2 140-3 140-4 140-5
141-1 141-2 141-3 141-4 141-5
142-1 142-2 142-3 142-4 142-5
143-1 143-2 143-3 143-4 143-5
144-1 144-2 144-3 144-4 144-5
145-1 145-2 145-3 145-4 145-5
146-1 146-2 146-3 146-4 146-5
147-1 147-2 147-3 147-4 147-5
148-1 148-2 148-3 148-4 148-5
149-1 149-2 149-3 149-4 149-5
150-1 150-2 150-3 150-4 150-5
151-1 151-2 151-3 151-4 151-5
152-1 152-2 152-3 152-4 152-5
153-1 153-2 153-3 153-4 153-5
154-1 154-2 154-3 154-4 154-5
155-1 155-2 155-3 155-4 155-5
156-1 156-2 156-3 156-4 156-5
157-1 157-2 157-3 157-4 157-5
158-1 158-2 158-3 158-4 158-5
159-1 159-2 159-3 159-4 159-5
160-1 160-2 160-3 160-4 160-5
161-1 161-2 161-3 161-4 161-5
162-1 162-2 162-3 162-4 162-5
163-1 163-2 163-3 163-4 163-5
164-1 164-2 164-3 164-4 164-5
165-1 165-2 165-3 165-4 165-5
166-1 166-2 166-3 166-4 166-5
167-1 167-2 167-3 167-4 167-5
168-1 168-2 168-3 168-4 168-5
169-1 169-2 169-3 169-4 169-5
170-1 170-2 170-3 170-4 170-5
171-1 171-2 171-3 171-4 171-5
172-1 172-2 172-3 172-4 172-5
173-1 173-2 173-3 173-4 173-5
174-1 174-2 174-3 174-4 174-5
175-1 175-2 175-3 175-4 175-5
176-1 176-2 176-3 176-4 176-5
177-1 177-2 177-3 177-4 177-5
178-1 178-2 178-3 178-4 178-5
179-1 179-2 179-3 179-4 179-5
180-1 180-2 180-3 180-4 180-5
181-1 181-2 181-3 181-4 181-5
182-1 182-2 182-3 182-4 182-5
183-1 183-2 183-3 183-4 183-5
184-1 184-2 184-3 184-4 184-5
185-1 185-2 185-3 185-4 185-5
186-1 186-2 186-3 186-4 186-5
187-1 187-2 187-3 187-4 187-5
188-1 188-2 188-3 188-4 188-5
189-1 189-2 189-3 189-4 189-5
190-1 190-2 190-3 190-4 190-5
191-1 191-2 191-3 191-4 191-5
Showing 162 to 168 of 5,000,000 entries
JavascriptHTMLCSSAjaxComments (0)
The Javascript shown below is used to initialise the table shown in this example:

$(document).ready(function() {
$(‘#example’).DataTable( {
serverSide: true,
ordering: false,
searching: false,
ajax: function ( data, callback, settings ) {
var out = [];

for ( var i=data.start, ien=data.start+data.length ; i<ien ; i++ ) {
out.push( [ i+'-1', i+'-2', i+'-3', i+'-4', i+'-5' ] );

setTimeout( function () {
callback( {
draw: data.draw,
data: out,
recordsTotal: 5000000,
recordsFiltered: 5000000
} );
}, 50 );
scrollY: 200,
scroller: {
loadingIndicator: true
stateSave: true
} );
} );
In addition to the above code, the following Javascript library files are loaded for use in this example:
Other examples
Basic initialisation
State saving
Client-side data source (50,000 rows)
Server-side processing (5,000,000 rows)
FixedColumns integration
Select integration
Bootstrap 4
Semantic UI
jQuery UI
DataTables designed and created by SpryMedia Ltd.
© 2007-2018 MIT licensed. Privacy policy. Supporters.
SpryMedia Ltd is registered in Scotland, company no. SC456502.

Opener Blackfly

Opener Blackfly

About Us
Sign up to receive news, events, and product updates.
A New Dimension of Travel
Watch our launch video

We spend too much time confined to a two-dimensional network of concrete and asphalt. The dream of futurists has always been a flying vehicle capable of efficiently moving passengers from A to B.

Opener is realizing this dream in an affordable, safe, easy-to-operate, vertical take-off and landing (VTOL) vehicle: BlackFly.

Opener’s BlackFly heralds a new era of aviation. Time and money spent traveling and maintaining infrastructure will be reduced. People will go places they never thought possible.

12,000+ miles flown

1,400+ flights

Safety first
At Opener, we designed a new aircraft with safety as our highest priority. Fitted with triple-modular redundant flight systems, control surfaces, and sensors, our aircraft provides a new way to confidently take to the skies.

Tried and tested
> 12,000 miles flown with payload
> 40,000 full-length propulsion system flight cycles: equivalent to 25 circumnavigations of the earth
Fault-tolerant design
Ease of operation
Simple user interface
Backup landing systems

Powerful Capabilities
Watch our flight video
Vertical Take-off and Landing (VTOL)

All Electric
Simple, safe, no emissions

Personal Aerial Vehicle (PAV)
Full freedom

Energy Consumption

245 Wh/mi
Electric Car

270 Wh/mi
Gasoline Car

1233 Wh/mi
Measured at 150 ft

72 dBA

76 dBA

80+ dBA

BlackFly Specifications
Single seat

PAV (Personal Aerial Vehicle)

VTOL (Vertical Take-Off and Landing)

Fixed tandem-wing aircraft

Full electric propulsion

Ultralight (USA)
Basic Ultralight (Canada)
Amphibious-capable (freshwater)
Joystick, fly-by-wire electrical controls

Epoxy-impregnated carbon fiber

Landing surfaces
Grass, asphalt, snow, ice

Triple-modular redundancy

Fault-tolerant design

8 fixed propulsion units

4 redundant elevon pairs

Ballistic parachute (optional)

Operating conditions
25 mph max wind (take-off and landing)

0 – 30 °C temperature range


Up to 6 ft 6 in / 250 lbs (USA)

13 ft 7 in wide

13 ft 5 in long

5 ft high

313 lbs (empty) (USA)
250 lbs (max. payload) (USA)
8 kWh (USA)
12 kWh (Intl)
Charging (Intl)
120 V / 15 A 20% – 100% Charge 7.4 hrs
120 V / 20 A 20% – 100% Charge 5.5 hrs
240 V / 50 A 20% – 100% Charge 67 mins
240 V / 2×50 A 20% – 80% Charge 25 mins
Range (with reserve)
25 miles (USA)
40+ miles (Intl)
Static thrust (max.)
900+ lbs
Performance (Max Take-off Weight)
Cruise Speed 62 mph (limited, USA)
80+ mph (Intl)
Stall speed 0 mph
Max. climb rate 1000 fpm
Max. descent rate 1000 fpm
Take-off run 36 in
Landing distance 36 in

A Complete Solution
Watch our features video
Disassembles and fits within a small trailer

Easy Assembly
From storage to sky in 30 minutes

Super Charging
80% charge in 25 minutes

Operates in multiple environments

Sign up to receive news, event, and product updates

Opener © 2018

Pine64 Single Board Computer

Pine64 Single Board Computer

Skip to content
64-bit Single Board Computer

Frequently Asked Questions
Here are some of the most frequently asked questions regarding the PINE64. If you don’t see your question here, please visit Pine64 forum,, for more info. Thank You!

What is Single Board Computer?
A single-board computer (SBC) is a complete computer built on a single circuit board with microprocessor(s), memory, input/output (I/O) and other features required for a functional computer. SBC were made as demonstration or development systems, for educational systems, or for use as embedded computer controllers. Many types of home computer and portable computer integrated all their functions onto a single printed circuit board.

What is Pine A64?
The Pine A64 is an index card sized 64-bit single board computer. It can perform like your desktop or portable PC with browsing the Internet, playing games, watching video, and execute programs like spreadsheets and word-processing. The Pine A64 board can also play ultra high definition 4Kx2K video.

Why 64-bit processors really matters?
The ARM 64-bit processor significantly increases performance over its 32-bit counterpart. Besides the performance increase, the 64-bit processor is more power efficient and consumes less energy.

How powerful is Pine A64 CPU processors?
The Pine A64 CPU is quad-core ARM A-53 64-bit processor and runs at 1.2GHz. The CPU’s MIPS benchmarks around 11,040 which makes it capabilities roughly equivalent to the Sony PS3’s level of performance or a netbook running AMD E-240 CPU at 1.5GHz.

How powerful is Pine A64 GPU processors?
The Pine A64 GPU is dual-core MALI-400 MP2 and runs at 500MHz, capable of 1.1 Gpixel/s throughput. Graphics capabilities are slightly higher than the original Xbox’s level of performance. The GPU provides OpenGL ES 2.0, hardware-accelerated OpenVG, 4Kx2Kp30 H.265 decode, and 1080p60 H.264 high-profile encode and decode.

Does Pine A64 board need a heatsink?
The SoC chip used in the Pine A64 is the same SoC design that is used in a tablet. Heatsink requirement will directly influenced by each application and case design.

What type of hardware interfaces that Pine A64 have?
Depending on the model, all the Pine A64 has 46 dedicated GPIO pins, three UART, two i2c bus, two SPI bus, i2s audio, SPDIF out, IR receiver, Speaker out, 3v3, 5v, and ground. In the “PLUS” model, there are additional three ports: CSI-Camera, Touch Control, and DSI-LCD Panel.

Can I add additional system memory?

What is Pine A64 operating temperature?
The Pine A64 operating temperature qualified range from -20°C to 70°C.

What is the difference between “BASIC” and “PLUS” model?
Two models are available: Pine A64 “BASIC” and the Pine A64+ “PLUS.” The “BASIC” model is the low-cost variant of the Pine A64 board. It has 512MB system RAM and 10/100 Mbps Ethernet port. The Pine A64+ “PLUS” model has 1GB system RAM, Gigabit Ethernet port, camera port, LCD panel display port, and touch control port. For Android users, we strongly recommend the Pine A64+ “PLUS” model due to the larger system memory size and for a better user experience.

Can I connect a keyboard and mouse to the Pine A64 and act as a computer?
Yes, most existing USB keyboard and mouse can work with the Pine A64 board.

What are the Pine A64 dimensions? What about the weight?
The Pine A64 board measures 127mm x 79mm x 21mm (or roughly 5.00″ x 3.11″ x 0.83″) at 46 grams.

Which SoC are used in the Pine A64 boards?
Both BASIC and PLUS model uses the Allwinner A64 SoC. The SoC contains a quad-core ARM Cortex A53 64-bit CPU with floating point, running at 1.2Ghz, and a dual-core MALI-400 MP2 GPU running at 500MHz. The GPU has a high performance 3D core accessed using the supplied OpenGL ES2.0 and OpenVG libraries.

Why use the Allwinner A64 SoC?
Cost, performance and reliability.

How does the Pine A64 boot?
With the microSD card inserted in the card slot, all files necessary for booting should be installed in a microSD card with FAT32 partition.

What operating systems do the Pine A64 board support?
Android Lollipop 5.1 or Ubuntu with Kernel 3.10 are available for you. Both comes with 64-bit version. For Android users, we recommend using Pine A64+ “PLUS” boards which has a larger system memory. In addition, we also work with openHAB ( for IoT (Internet of Things) application. The OS is stored on the microSD card; it is a straightforward process to replace the root partition on the microSD card with another ARM Linux.

Will the Pine A64 run Microsoft Windows or Windows RT OS?
No but we are working on it. Check back here frequently for updates.

Which Linux runs on the Pine A64 board?
Ubuntu and Debian runs on the Pine A64 board.

Can the Pine A64 run Android?
Yes, Android Lollipop 5.1 64-bit OS runs natively in Pine A64 board. We strongly advise you run Android on Pine A64+ “PLUS” model due to the larger system memory size for a better user experience.

What is the power requirement?
The board is powered by +5v microUSB port. Exactly how much power is required, in terms of current. (mA), is depending on what you hook up to the board. An official 2.0A (2000mA) power supply is available at the Pine64 store with ample power to run the board for most applications.

What is size of the microSD card I need?
For Linux OS, the minimum microSD size can be as low as 4GB. For Android OS, we recommend no less than 8GB. Besides OS space requirement, please also calculate the free space you need to install additional packages or make programs/data of your own.

What capacity of the microSD card can the Pine A64 support?
The Pine A64 board supports SD, SDHC, and SDXC format microSD card – this means the largest capacity is 256GB. Please note that if a microSD card is formatted as an FAT32 file format, the maximum capacity is 32GB.

How about support for other storage devices?
You can also attach a USB stick or USB hard drive to provide extra storage.

What happens when the Pine A64 board brick?
Just simply restore the Pine A64 board by re-flashing the microSD card.

Does the Pine A64 support networking?
The “BASIC” model has built in 10/100Mbps wired Ethernet and “PLUS” model has built in Gigabit wired Ethernet. There is a Wi-Fi and Bluetooth native expansion port on both models.

Is there wireless expansion for Wi-Fi and Bluetooth?
Yes, the Pine A64 has the reserved expansion port for Wi-Fi and Bluetooth. The various Wi-Fi and Bluetooth daughter boards are available at Pine64 store (

Is sounds supported through HDMI?

Is sounds supported through SPDIF?
Yes it is through the output port located at the “euler“ bus connector.

Is there a mic port on the Pine A64?
The Pine A64 audio 3.5mm mini-jack supports microphone function from your headphones. A USB webcam with microphones function also another solution.

What about standard audio in and out?
The Pine A64 audio 3.5mm mini-jack supplies amplified audio output to your headphone; you can also use as audio line out. You can add USB microphone support devices, such as webcam for audio in, or using the I2S interface on the “euler” bus connector for additional audio I/O function.

What display monitor can I use?
There is an HDMI port on the Pine A64 board, and you can hook up to a HDMI monitor or HDTV. For the DVI monitor connection, a passive HDMI->DVI adapter is needed. There is no VGA nor Composite Video support on the Pine A64 board, but such active HDMI->VGA or HDMI->Composite Video converter is available and can be purchased directly at the Pine64 store (

Can I stream Netflix?
Yes! Pine64 can run Nextflix in SD video.

Which HDMI version is supported?
Version 1.

What are the video specifications supported by the Pine A64 board?
•H.265 4K@30fps video decoding
•multi-format 1080p@60fps video decoding, including H.264 BP/MP/HP, VP8, MPEG 1, MPEG2, MPEG4 SP/ASP GMC, H.263 including Sorenson Spark, VC1/WMV9, MJPEG and etc.
•H.264 1080p@60fps or 720p@120fps video encoding

What is the DSI port?
The LCD Panel port is a 4 lane MIPI DSI up to 1920×1200@60fps. It provides connectivity to an LCD panel and turns the Pine A64 into a computer or tablet.

What model of the LCD panel is compatible for the Pine A64?
We currently offer a 7 inch color active matrix 1024 x 600 LCD panel with 24 chip LED backlight.

What is a Camera Card?
The Camera Card is a small PCB that connects to the CSI camera port on the Pine A64 using a short ribbon cable. It provides connectivity for a camera to capture still images or video recordings.

What is the model of the camera chip?
5megapixels CMOS camera chip.

What is the camera specification?
The camera card specifications are as follows:
•Aperture: f2.8
•Focal length: 2.7mm
•Shooting range: 0.2m→∞
•Field of view: 66 degree
•Optical Distortion: 0.24%
•White balance: Automatic
•Gain: Automatic
•Exposure control: Automatic

What is the camera resolution?
The camera card is capable of taking images up to 5 megapixels (5MP) (2592×1944 pixels) and video recordings at resolutions up to 720p30.

What picture formats does the camera card support?
The camera card supports raw capturing, uncompressed YUV, JPEG422, RGB565, RGB555, and RGB444 photos. It also records H.264 video.

Does the Pine A64 come with a case?
Various official cases for the Pine A64 are available at Pine64 store.

Does the Pine A64 support IR receivers?
Yes, the Pine A64 board has reserved connectors for IR receivers and also introduces an official IR remote control that is available at Pine64 store.

Does the Pine A64 have the Real-Time Clock (RTC) feature?
Yes, the Pine A64 board comes with the RTC feature. The clock power source can be either come from optional 3V Lithium coin battery or Lipo battery.

Where can I purchase the Pine A64 board cost?
You can purchase the Pine A64 directly on

How much does the Pine A64 board cost?
The “BASIC” model costs $15.25, and the “PLUS” model costs $19.50, plus local taxes if applicable and shipping/handling fees.

What else will I need after I purchase the Pine A64 board?
Once you purchase the Pine A64 board, you will also need a power supply and microSD card for boot up (which are not included in the board purchase). The power supply and microSD card are available for purchase on our online store.

Is the Pine A64 available worldwide?

Contact Us

Find Us
About Us

Media Coverage
Subscribe to Newsletter

Shipping Policy
Warranty Policy
Cancellation & Refunds
Return & Refund Policies
Terms & Conditions
Privacy Policy
Terms of Use
Copyright © 2018 PINE64. All rights reserved.

Harvard Oliver Knill Mathematics and Physics

Harvard Oliver Knill Mathematics Physics

Index of /archive/118r_spring_05/handouts
Icon Name
[DIR] Parent Directory
[ ] 2dperiodic.pdf
[ ] 3dexamples.pdf
[ ] approximation.pdf
[ ] archimedes.pdf
[ ] bernoulli.pdf
[ ] billiard.pdf
[ ] caintro.pdf
[ ] caustic.pdf
[ ] caustics.pdf
[ ] chaotic.pdf
[ ] complex.pdf
[ ] conclusion.pdf
[ ] dynamicalsystems.pdf
[ ] entropy.pdf
[ ] escape.pdf
[ ] examples.pdf
[ ] existence.pdf
[ ] exterior.pdf
[ ] feigenbaum.pdf
[ ] fixedpoint.pdf
[ ] fractal.pdf
[ ] geodesic.pdf
[ ] geodesics.pdf
[ ] hedlund.pdf
[ ] henon.pdf
[ ] hilbert.pdf
[TXT] hint6.txt
[ ] homework.pdf
[ ] homework1.pdf
[ ] homework10.pdf
[ ] homework11.pdf
[ ] homework2.pdf
[ ]
[ ] homework3.pdf
[ ] homework4.pdf
[ ] homework5.pdf
[ ] homework6.pdf
[ ] homework7.pdf
[ ] homework8.pdf
[ ] homework9.pdf
[ ] hopf.pdf
[ ] horseshoe.pdf
[ ] ice1.pdf
[ ] ice2.pdf
[ ] integrable.pdf
[ ] introduction.pdf
[ ] lattice.pdf
[ ] lecture1.pdf
[ ] lecture2.pdf
[ ] lecture3.pdf
[ ] lienard.pdf
[ ] life.pdf
[ ] linearization.pdf
[ ] lorentz.pdf
[ ] lorentz2.pdf
[ ] lyapunov.pdf
[ ] mandelbrot.pdf
[ ] measure.pdf
[ ] minimal.pdf
[ ] nbody.pdf
[ ] openproblems.pdf
[ ] poincare.pdf
[ ] polygonal.pdf
[IMG] poster.gif
[ ] preliminaries.pdf
[ ] project.pdf
[ ] quiz.pdf
[ ] quizz11.pdf
[ ] rest.pdf
[IMG] roessler.gif
[ ]
[ ] shift.pdf
[ ] sitnikov.pdf
[ ] survival.pdf
[ ] symbolic.pdf
[ ] text.pdf
[ ] turing.pdf
[ ] vlasov.pdf
[ ] weyl.pdf
[ ] zeipel.pdf
Apache/2.2.15 (Red Hat) Server at Port 80

The Monte-Carlo Method (Little Mathematics Library)

The Monte-Carlo Method (Little Mathematics Library)

Everybody had at some moment used the words âprobabilityâ
and ârandom variableâ. The intuitive idea of the probability (considered as frequency) corresponds more or less to the true meaning of this concept. But as a rule the intuitive idea of the random variable differs quite considerably from the mathematical definition. Thus, the notion of the probability is assumed known in Sec. 2, and only the more complicated notion of the random variable is clarified. This section cannot replace a course in the probability
theory: the presentation is simplified and proofs are omitted.
But it still presents certain concept of the random variables sufficient for understanding of Monte Carlo techniques.

The basic aim of this book is to prompt the specialists in various branches of knowledge to the fact that there are problems in their fields that can be solved by the Monte Carlo method.

Creating / renewing a Let’s Encrypt certificate for Apache and WildFly

Creating / renewing a Let’s Encrypt certificate for Apache and WildFly

These instructions were written for Ubuntu 16, but they should translate quite easily to other flavours of *nix, relatively easily for macOS, and with only small tweaks for Windows. Probably.

Contents [hide]

1 Apache
1.1 Installing certbot
2 WildFly
2.1 Converting the PEM file
2.2 Generating the keystore
Renewing the Apache portion of the certificate is fairly easy – Let’s Encrypt’s certbot can handle that for you. In my case, I’d not renewed since the certbot was brought in, so a bit of installation was required.

Installing certbot
I have some locale settings issues on my box. I’m not certain if that’s because I mucked something up or there’s some weird defaults, but I need to manually set the locale before a lot of things. Yes, I should really stick it into a startup script, but I tend to forget about it the moment I’m done with it. Perhaps after this article.

In any case, to set some locale settings so that install will work, enter

export LC_ALL=C

export LC_ALL=C
To install the certbot from scratch, I followed the instructions here. I’ll repeat the easy parts below, and include parts on renewal, but you should read through that article for a more in-depth treatment and your initial certificate generation. Note that some of these commands require sudo access, so it might be easier to paste them in one at a time – at least for the first one, so that you can type in your password. I didn’t do that, and it was relatively exciting afterwards.

Not bad, just relatively exciting. Anyways, to install certbot:

sudo mkdir /opt/certbot
cd /opt/certbot
sudo wget
sudo chmod a+x certbot-auto

sudo mkdir /opt/certbot
cd /opt/certbot
sudo wget
sudo chmod a+x certbot-auto
Now that certbot is (hopefully) installed, we need to ask it to renew our certificate. If you’re setting up an initial certificate, see this link again. To renew the certificate, just issue a command like

/opt/certbot/certbot-auto renew

/opt/certbot/certbot-auto renew
Many many status messages will scroll down, finishing with something like (for an Apache setup)

new certificate deployed with reload of apache server; fullchain is

new certificate deployed with reload of apache server; fullchain is
With YOURDOMAIN replaced with your actual domain, obviously.

Next up, we need to get the public and private keys into Wildfly. Apache was setup with the public and private keys pointed to separately, but Wildfly (well, Java) works off of a keystore. What we’re going to do is generate a new keystore that contains your new private and public keys, as read off of the /etc/letsencrypt/live/YOURDOMAIN/fullchain.pem file that certbot generated earlier.

Converting the PEM file
To do this, we need to convert the PEM file into a P12 file that is readable by the keytool. This is accomplished by issuing the OpenSSL command, after making suitable replacements.

sudo openssl pkcs12 -export -in /etc/letsencrypt/live/YOURDOMAIN/fullchain.pem -inkey /etc/letsencrypt/live/YOURDOMAIN/privkey.pem -out YOURKEYSTORENAME.p12 -name KEYSTOREALIAS

sudo openssl pkcs12 -export -in /etc/letsencrypt/live/YOURDOMAIN/fullchain.pem -inkey /etc/letsencrypt/live/YOURDOMAIN/privkey.pem -out YOURKEYSTORENAME.p12 -name KEYSTOREALIAS
The YOURDOMAIN replacement is the folder corresponding to the domain that you’re generating the key for, and was present in the listed output from the previous step. The KEYSTORENAME will become part of the generated file name, and will be used in the WildFly configuration, as will the KEYSTOREALIAS. These can be anything of your choice. Once you’ve pressed enter, you’ll be prompted (and verified) for a new password. This new password will be used in a moment when we generate the keystore.

You may not need the sudo part of the command, but you more likely will as people shouldn’t generally have read permissions to the various keys.

Generating the keystore
Once the certificate has been converted, we need to produce the keystore. This again is a one-liner with some substitutions:

keytool -importkeystore -deststorepass WILDFLY_NEW_STORE_PASS -destkeypass WILDLFY_NEW_KEY_PASS -destkeystore NEW_KEYSTORE_FILE.jks -srckeystore YOURKEYSTORENAME.p12 -srcstoretype PKCS12 -srcstorepass PREVIOUSPASSWORD -alias KEYSTOREALIAS
keytool -importkeystore -deststorepass WILDFLY_NEW_STORE_PASS -destkeypass WILDLFY_NEW_KEY_PASS -destkeystore NEW_KEYSTORE_FILE.jks -srckeystore YOURKEYSTORENAME.p12 -srcstoretype PKCS12 -srcstorepass PREVIOUSPASSWORD -alias KEYSTOREALIAS
There are a couple of substitutions here – new ones are a password for the keystore, a password for the key within the keystore, and the name of the resulting keystore. The other substitutions are either from the previous step, or from the password created as part of the previous step.

This will result in a keystore with your chosen name being generated in your current folder. You can copy this to your WildFly’s configuration folder, e.g.

sudo cp NEW_KEYSTORE_FILE.jks /opt/wildfly/standalone/configuration/

sudo cp NEW_KEYSTORE_FILE.jks /opt/wildfly/standalone/configuration/
WildFly configuration

Finally, we need to add the keystore to WildFly. There are many posts detailing how to set up SSL for WildFly, and this is really more focused on renewing certificates, so we’ll check just that. Find the section, and specifically the one you’re setting up – Undertow in my case.

Update your tag as

Reboot WildFly with


sudo system wildfly restart

sudo system wildfly restart
And you’re all done. For a coupla months.